[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: more details for errors
From: |
Thomas Dickey |
Subject: |
Re: more details for errors |
Date: |
Mon, 21 Jun 2004 17:22:37 -0400 (EDT) |
On Mon, 21 Jun 2004, Folkert van Heusden wrote:
> > > Some functions return an errorcode when something fails, like ERR or NULL.
> > > That is not so helpfull in all situations :)
> > > Maybe adding something that logs to syslog or something?
> > > Like: ncurses checks for an environment ('NCURSES_DO_ERROR_LOG' or so)
> > > being
> > > set and then logs to syslog.
> > The debug library has a trace feature which shows the parameters for
> > most (perhaps all) of the ncurses functions. It also shows the return
> > value.
>
> Yes, but it doesn't show the reason why it failed, or does it? Like:
> subwin() failed because parameters out of range or so or no memory. Stuff
> like that.
not in a text form - that could be enhanced, true.
(but I am usually looking at the source code to see what the trace
tells me).
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net