Re: GLib-GObject-CRITICAL debugging

[Daniel Piccoli <d piccoli murdoch edu au>]

Thanks Denis,

I'm not very experienced with gdb. I set G_DEBUG to fatal_warnings and
got the following backtrace after the program aborted.

(gdb) bt
#0  0x4064ae31 in kill () from /lib/libc.so.6
#1  0x4064abd5 in raise () from /lib/libc.so.6
#2  0x4064c19b in abort () from /lib/libc.so.6

Is there any way to get back to where my code called these functions?

Thanks.