Hi Dan,
[snip]
>I'm trying to track down the source of the warning in the subject line.
> So I ran my program in the debugger and used the --g-fatal-warnings
>command line argument to my program. Running gives:
>
[snip]
>Any suggestions on how to debug this short of inserting a pile of
>printf's and trying to isolate it that way?
You might want to try:
--gtk-debug options. A list of debug options to turn on in addition to those
specified in the GTK_DEBUG environment variable. This option is only available
if GTK+ has been configured with --enable-debug=yes.
or
GTK_DEBUG. If GTK+ has been configured with --enable-debug=yes, this variable
can be set to a list of debug options, which cause GTK+ to print out different
types of debugging information.
misc
...
The special value all can be used to turn on all debug options.
http://developer.gnome.org/doc/API/2.0/gtk/gtk-running.html
You will probably have to rebuild your gtk+ (with --enable-debug=yes and
the other debugging features), but that should be really easy since all
the dependancies are already installed.
However, going the printf approach is probably the least amount of pain,
as it looks like this warning is caused by some sort of callback function
or update (hence the somewhat empty/useless stack).
Also, rebuilding gtk+ with debugging enabled (-g) might give you more useful
info in this limited stack trace.
-Ales
_______________________________________________
geda-dev mailing list
[email protected]
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
