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



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?

Its a fairly large window, so i'd rather not have to resort to trial and
error, but i suppose if it comes to that, its better than a crashing
program -_^

Thanks

On Sun, 2003-02-02 at 19:29, Raymond Wan wrote:
> Hi,
> 
> 	I can't remember if this was valid for 1.2, but try running it
> with gdb with the "--g-fatal-warnings" flag.  i.e., within gdb, do "run
> --g-fatal-warnings <your program arguments>".  That has helped me in the
> past, though I can't remember if I used it with 1.2 .
> 
> Ray
> 
> On 2 Feb 2003, Brenden Conte wrote:
> 
> > forgot to mention, this is with 1.2
> > 
> > On Sun, 2003-02-02 at 12:49, Brenden Conte wrote:
> ...
> > > However, if i switch gtk_widget_destroy with gtk_widget_hide, there are
> > > no errors.  This tells me that there is something inside the window that
> > > is causing this, but the error is useless in trying to find this
> > > problem.
> > > 
> > > Does anyone have suggestions of how i might find what exactly is causing
> > > this?
> 
> 
> _______________________________________________
> gtk-list mailing list
> gtk-list gnome org
> http://mail.gnome.org/mailman/listinfo/gtk-list
-- 
Brenden Conte <conteb alum rpi edu>




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]