Hi, On jeu, fév 17, 2005, Francesco Potorti` wrote: > I tried twice, as you see in the following. I'll try again, and let you > know.
Strangely, your stack traces seem truncated. > $ LD_LIBRARY_PATH=/usr/lib/debug/: gdb galeon (Warning there's a ":".) > (galeon:6466): Gtk-CRITICAL **: gtk_container_foreach: assertion > `GTK_IS_CONTAINER (container)' failed (That is now clearer to me I think, it seems to be l = gtk_container_get_children (GTK_CONTAINER (dock)); in libegg/egg-editable-toolbar.c:166.) > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 16384 (LWP 6466)] Please note, "Thread 16384 (LWP 6466)". > 0x08176b2c in get_toolbar_nth (etoolbar=0x86d7a88, position=1) at > egg-editable-toolbar.c:167 > 167 egg-editable-toolbar.c: No such file or directory. > in egg-editable-toolbar.c This is very interesting, as it is now correct! :) > (gdb) thread apply all bt full This requests the stack trace of all threads. > Thread 4 (Thread 32771 (LWP 6479)): This is the first stack trace, for the first thread, but were are the other threads?!? > (gdb) r again... > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 16384 (LWP 6907)] okay, the segfault is in Thread 16384 (LWP 6907) > (gdb) thread apply all bt full > Thread 9 (Thread 114696 (LWP 7091)): first thread... ... and no other? Maybe gdb is borken, if you really don't get the stack traces for more than one thread, please give me the output of: bt full instead of "thread apply all bt full", so I'll get the stack trace in the thread which segfaults. Thanks! -- Loïc Minier <[EMAIL PROTECTED]> "Neutral President: I have no strong feelings one way or the other."
