aMule Forum

English => Backtraces => Topic started by: stefanero on October 10, 2004, 04:50:29 PM

Title: aaaaaahhhhhhhhhhhhh ;)
Post by: stefanero on October 10, 2004, 04:50:29 PM
current CVS from 10.10---with wx-cvs

Quote
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 30954)]
0x402fd374 in gtk_frame_focus_out_callback ()
   from /usr/lib/libwx_gtk_core-2.5.so.3
(gdb) bt
#0  0x402fd374 in gtk_frame_focus_out_callback ()
   from /usr/lib/libwx_gtk_core-2.5.so.3
#1  0x40658bf8 in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0
#2  0x08e17c88 in ?? ()
#3  0x08dacc1c in ?? ()
#4  0x08e17a68 in ?? ()
#5  0x082afa71 in CamuleApp::NotifyEvent (this=0x8b2f960, event=Cannot access memory at address 0xb0
)
    at amule.cpp:2051
#6  0x00009a15 in ?? ()
#7  0x08b2f960 in ?? ()
#8  0x000000b0 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(gdb) bt full
#0  0x402fd374 in gtk_frame_focus_out_callback ()
   from /usr/lib/libwx_gtk_core-2.5.so.3
No symbol table info available.
#1  0x40658bf8 in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0
No symbol table info available.
#2  0x08e17c88 in ?? ()
No symbol table info available.
#3  0x08dacc1c in ?? ()
No symbol table info available.
#4  0x08e17a68 in ?? ()
No symbol table info available.
#5  0x082afa71 in CamuleApp::NotifyEvent (this=0x8b2f960, event=Cannot access memory at address 0xb0
)
    at amule.cpp:2051
No locals.
#6  0x00009a15 in ?? ()
No symbol table info available.
#7  0x08b2f960 in ?? ()
No symbol table info available.
#8  0x000000b0 in ?? ()
No symbol table info available.


happens when you change quit a bit in prefs...pretty easy to repeat

stefanero
Title: Re: aaaaaahhhhhhhhhhhhh ;)
Post by: stefanero on October 12, 2004, 07:00:01 AM
hmmmm
this is getting silly.....
now same crash like prefs but while minimizing to tray

Quote
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7158)]
0x402f93c4 in gtk_frame_focus_out_callback () from /usr/lib/libwx_gtk_core-2.5.so.3
(gdb) bt
#0  0x402f93c4 in gtk_frame_focus_out_callback () from /usr/lib/libwx_gtk_core-2.5.so.3
#1  0x40654bf8 in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0
#2  0x08b21910 in ?? ()
#3  0x08dbe590 in ?? ()
#4  0x08b23ff0 in ?? ()
#5  0x4056f1aa in wxEventHashTable::HandleEvent () from /usr/lib/libwx_base-2.5.so.3
#6  0x00009a15 in ?? ()
#7  0x08b22068 in ?? ()
#8  0x000000b0 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(gdb) bt full
#0  0x402f93c4 in gtk_frame_focus_out_callback () from /usr/lib/libwx_gtk_core-2.5.so.3
No symbol table info available.
#1  0x40654bf8 in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0
No symbol table info available.
#2  0x08b21910 in ?? ()
No symbol table info available.
#3  0x08dbe590 in ?? ()
No symbol table info available.
#4  0x08b23ff0 in ?? ()
No symbol table info available.
#5  0x4056f1aa in wxEventHashTable::HandleEvent () from /usr/lib/libwx_base-2.5.so.3
No symbol table info available.
#6  0x00009a15 in ?? ()
No symbol table info available.
#7  0x08b22068 in ?? ()
No symbol table info available.
#8  0x000000b0 in ?? ()
No symbol table info available.
(gdb)  

!?!
Title: Re: aaaaaahhhhhhhhhhhhh ;)
Post by: Kry on October 12, 2004, 03:16:45 PM
I'm starting to bet it's your fault
Title: Re: aaaaaahhhhhhhhhhhhh ;)
Post by: stefanero on October 12, 2004, 07:00:52 PM
ok,
seams to be a wx-cvs problem, I checked out wx-cvs from 10days ago

no problem at all...will try now offical 2.5.3 tar.gz

stefanero