[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Debug output etc, cluttering the terminal

On Sun, 2010-08-15 at 17:02 +0100, Neil Williams wrote:
> Most of the stuff in ~/.xsession-errors which has been mentioned here,
> are exactly these kind of assertion failure errors:
> (gnome-power-manager:2346): GLib-GObject-WARNING **: value "-nan" of
> type `gdouble' is invalid or out of range for property `percentage' of
> type `gdouble'
> (polkit-gnome-authentication-agent-1:2468): GLib-CRITICAL **:
> g_once_init_leave: assertion `initialization_value != 0' failed
> Those are BUGS. It might not cause symptoms now but it is still
> relevant to how other bugs in that application are triaged. The
> upstream code needs to be fixed to check these values before passing
> them to the relevant function.

I mostly agree with this.  These are warnings, not simply debug
information, and the application author should fix them.  However, each
specific warning should only be printed once, since that's enough to
indicate the existence of the bug.

> Not a default across all packages and all debug output but there are
> situations where *some* debug output needs to be part of the default
> output of the application in order to actually capture the data
> necessary to fix the bugs.
> Some applications, even some mature applications, need to be able to
> output debug information to the controlling terminal as a matter of
> course in order to fix unreproducible and/or intermittent bugs.

This is nonsense.  What the application authors need in this case is
logging, and writing to stderr is not logging (modulo use of e.g.
systemd to capture stderr).  They need to open an application- and
user-specific log file and write to that instead.


Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply to: