aMule Forum
English => Backtraces => Topic started by: fctk on January 22, 2005, 02:13:30 PM
-
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1223379264 (LWP 8703)]
0xb7ca1514 in gtk_frame_focus_out_callback ()
from /usr/lib/libwx_gtk2u_core-2.5.so.3
(gdb) bt
#0 0xb7ca1514 in gtk_frame_focus_out_callback ()
from /usr/lib/libwx_gtk2u_core-2.5.so.3
#1 0xb77d6fe5 in gtk_marshal_VOID__UINT_STRING ()
from /usr/lib/libgtk-x11-2.0.so.0
#2 0xffffffff in ?? ()
#3 0x086441f0 in ?? ()
#4 0x088c8150 in ?? ()
#5 0xb76168f7 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#6 0xbffff08c in ?? ()
#7 0x00000000 in ?? ()
#8 0x00000000 in ?? ()
#9 0x00000000 in ?? ()
#10 0xb77d6f6c in gtk_marshal_VOID__UINT_STRING ()
from /usr/lib/libgtk-x11-2.0.so.0
#11 0xb7625e7c in g_signal_has_handler_pending ()
from /usr/lib/libgobject-2.0.so.0
Previous frame inner to this frame (corrupt stack?)
(gdb) bt full
#0 0xb7ca1514 in gtk_frame_focus_out_callback ()
from /usr/lib/libwx_gtk2u_core-2.5.so.3
No symbol table info available.
#1 0xb77d6fe5 in gtk_marshal_VOID__UINT_STRING ()
from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#2 0xffffffff in ?? ()
No symbol table info available.
#3 0x086441f0 in ?? ()
No symbol table info available.
#4 0x088c8150 in ?? ()
No symbol table info available.
#5 0xb76168f7 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
#6 0xbffff08c in ?? ()
No symbol table info available.
#7 0x00000000 in ?? ()
No symbol table info available.
#8 0x00000000 in ?? ()
No symbol table info available.
#9 0x00000000 in ?? ()
No symbol table info available.
#10 0xb77d6f6c in gtk_marshal_VOID__UINT_STRING ()
---Type to continue, or q to quit---
from /usr/lib/libgtk-x11-2.0.so.0
No symbol table info available.
#11 0xb7625e7c in g_signal_has_handler_pending ()
from /usr/lib/libgobject-2.0.so.0
No symbol table info available.
-
fctk,
The only thing I can extract from this bt is that the error occurred while GTK called a callback inside wxGTK-2.5.3. This is probably a problem inside wxGTK, check your compilation or version. If using a wxGTK from CVS, you must be somewhat carefull, sometimes things break.
Cheers!