Re: Finding cause of Gtk-CRITICAL in gtk_destroy_widget()

[Sven Neumann <sven gimp org>]

Hi,

Brenden Conte <conteb alum rpi edu> writes:

> Thanks for the input.  It appears to have killed the program
> immediately, but all that was left in the stack was a kill, raise, and
> abort - nothing i could use to track even the memory position or
> anything.  Did i need to compile it with special anything?

sure, you need to compile the library and your app with debugging
information to get a useful stack trace. You usually use the -g
compiler flag. Libraries such as glib and gtk+ often have a special
configure option to enable debugging info. Check the output of 
configure --help.


Salut, Sven