aMule Forum

English => Backtraces => Topic started by: NiKo87 on December 12, 2005, 11:32:16 PM

Title: aMule crashing on Mac OS X
Post by: NiKo87 on December 12, 2005, 11:32:16 PM
Hi, I compiled the 11/12 (12 December) CVS and after some minutes of activity aMule crashes. I used the wxMac 2.6.2

(gbd) bt
#0  0x93187efc in DequeueEvent ()
#1  0x93187db8 in AcquireEventFromQueue ()
#2  0x9318580c in ReceiveNextEventCommon ()
#3  0x9328adc8 in ReceiveNextEventInMode ()
#4  0x001c987c in wxApp::MacDoOneEvent () at StringFunctions.cpp:257
#5  0x001c9964 in wxApp::MainLoop () at StringFunctions.cpp:257
#6  0x002874ac in wxEntry () at kademlia/routing/RoutingBin.cpp:219
#7  0x000ac5c8 in main (argc=1, argv=0xbffffb04) at amule-gui.cpp:150
Title: Re: aMule crashing on Mac OS X
Post by: lionel77 on December 13, 2005, 12:23:48 AM
The actual error message is something like "Program received signal EXC_BAD_ACCESS, Could not access memory. 0x928accdc in DequeueEvent ()", right?

I experienced the same thing a week ago when I had build aMule CVS against wx 2.6.2 to investigate aMule's CPU hogging behavior further. With current wx CVS I don't get these crashes (or at least not at this high frequency).


EDIT:
In the future it would be great if you could post the actual error message and the output of "bt", "bt full", and "thread apply all bt" (see this thread (http://forum.amule.org/thread.php?threadid=7670&sid=) for more details). :)
Title: Re: aMule crashing on Mac OS X
Post by: NiKo87 on December 13, 2005, 12:03:12 PM
Where can I found the error message?
Today I'll try to compile using the wxWidgets CVS thanks :)
Title: Re: aMule crashing on Mac OS X
Post by: NiKo87 on December 13, 2005, 06:13:35 PM
Thanks, it works using the latest CVS of the wxMac.
Title: Re: aMule crashing on Mac OS X
Post by: lionel77 on December 14, 2005, 12:34:25 AM
I'm glad it's now woking for you. :)



Quote
Originally posted by NiKo87
Where can I found the error message?
It's simply the last couple lines from the terminal window before the gdb prompt.
For instance:
Code: [Select]
Program received signal EXC_BAD_ACCESS, Could not access memory.
0x0013a0a0 in wxStringBase::size() const (this=0x22e9ac) at /Applications/-other/wx/myWidgets_Debug/include/wx-2.7/wx/string.h:367
367       size_type size() const { return GetStringData()->nDataLength; }


(gdb) bt
[...]