Re: GLib-GObject-CRITICAL debugging
- From: Denis <denis lists gmail com>
- To: Daniel Piccoli <d piccoli murdoch edu au>
- Cc: gtk-app-devel-list gnome org
- Subject: Re: GLib-GObject-CRITICAL debugging
- Date: Fri, 13 May 2005 17:57:45 +0200
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 with -g in order to also have the stack
in the libs : it is very useful to understand errors in you code when
the doc lacks some explanations.
Hope this helps.
Denis.
Daniel Piccoli wrote:
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 particular g_signal_connect call is
causing this.
Thanks.
_______________________________________________
gtk-app-devel-list mailing list
gtk-app-devel-list gnome org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]