Thanks all,
I have implemented all suggestions including the idea of having a
separate debug installation of gtk. gdb now shows results in the detail
required including references to my files.
On Sat, 2005-05-14 at 18:15, Stefan Kost wrote:
Hi Daniel,
what I do is to have the same version of
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
Thanks Oliver,
I tried that but it is still the same. Do I have to have gtk+/glib etc
compiled with the debug option? (I use gentoo)
On Sat, 2005-05-14 at 17:19, Olivier Ramare wrote:
Hi,
I usually compile with the additionnal flag -ggdb
then gdb ./Sol.o (mine is called Sol.o these days :-))
Hi Daniel,
what I do is to have the same version of gtk and glib I have from portage
installed again to my homedir built from source.
So I have $HOME/debug with debug version of some libs. When I have to gebug I
just lauch the app as
env LD_LIBRARY_PATH=$HOME/debug/lib gdb ./my-app
Hi all,
Is there any easy way to debug GLib-GObject-CRITICAL runtime errors? I
am currently getting the following runtime error:
(app:9741): GLib-GObject-CRITICAL **: file gsignal.c: line 1543
(g_signal_connect_closure_by_id): assertion `signal_id 0' failed
It would be nice to know which
If you set the environment var G_DEBUG to fatal_warnings (export
G_DEBUG=fatal_warnings with bash), it should assert when there is an error.
If you launch your program with gdb, you will have the stack.
Another good idea I think is to have on your dev machine a
glib/atk/pango/gtk+ lib compiled
