Re: debugging information

[David Nečas (Yeti) <yeti physics muni cz>]

On Mon, Jun 19, 2006 at 05:20:05PM +0100, Yiannis wrote:
> Sorry if this is beyond the scope of this list.... but on the following
> message
>
> (md:2198): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT
> (object)' failed
>
> which is a runtime error I am wondering what is the (md:2198). Yes md is the
> program name... but the 2198

...is the process number.

> In other words is it
> possible to trace the file/function/line that this error is caused from?

If GLib was compiled with --enable-debug=yes, set

  G_DEBUG=fatal_criticals

before running the program and it will dump core on
a CRITICAL message.

The the same effect can be achieved programatically by
calling

  g_log_set_always_fatal(G_LOG_LEVEL_CRITICAL);

If none of above is possible you can set a breakpoint on
g_log in gdb and wait until the right message arrives.

Yeti


--
Anonyms eat their boogers.