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

2003-02-03 Thread Brenden Conte
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

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

2003-02-03 Thread Sven Neumann
Hi, Brenden Conte [EMAIL PROTECTED] 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

Finding cause of Gtk-CRITICAL in gtk_destroy_widget()

2003-02-02 Thread Brenden Conte
I have a line of code that looks like so: gtk_widget_destroy(GTK_WIDGET(windowlist_entry-window)); where window is a (void *) in a struct, windowlist_entry. Whenever this line is run, i get the error: Gtk-CRITICAL **: file gtkwidget.c: line 4880 (gtk_widget_unref): assertion `GTK_IS_WIDGET

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

2003-02-02 Thread Brenden Conte
forgot to mention, this is with 1.2 On Sun, 2003-02-02 at 12:49, Brenden Conte wrote: I have a line of code that looks like so: gtk_widget_destroy(GTK_WIDGET(windowlist_entry-window)); where window is a (void *) in a struct, windowlist_entry. Whenever this line is run, i get the error:

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

2003-02-02 Thread Raymond Wan
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