aMule Forum

English => Backtraces => Topic started by: sssnake on September 28, 2004, 09:02:48 AM

Title: backtrace under OS X (Version CVS from 20040927 20:54)
Post by: sssnake on September 28, 2004, 09:02:48 AM

Hi,
I have a backtrace here from amule under OS X from source from yesterday (see subject). I compiled it like described in this forum. First it runs fine for a long time, sying only

Code: [Select]

*** malloc[9742]: Deallocation of a pointer not malloced: 0x8043040; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debugfrom time to time. When I came back in the morning, amule was frozen and I had this output:

Code: [Select]

*** malloc[9742]: error for object 0x11d4ce90: Incorrect checksum for freed object - object was probably modified after being freed; break at szone_error
*** malloc[9742]: error for object 0x11d4ce90: Incorrect checksum for freed object - object was probably modified after being freed; break at szone_error
*** malloc[9742]: error for object 0x11bec590: Incorrect checksum for freed object - object was probably modified after being freed; break at szone_error

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x900015e4 in szone_free ()
(gdb) bt
#0  0x900015e4 in szone_free ()
#1  0x90195edc in CFRunLoopRunSpecific ()
#2  0x927d5f88 in RunCurrentEventLoopInMode ()
#3  0x927dc6f0 in ReceiveNextEventCommon ()
#4  0x9284d7fc in ReceiveNextEventInMode ()
#5  0x03e9051c in wxApp::MacDoOneEvent() ()
#6  0x03e901b0 in wxApp::MainLoop() ()
#7  0x03bc0468 in wxEntry(int&, char**) ()
#8  0x0013b684 in main (argc=1, argv=0xbffffc3c) at amule.cpp:176
(gdb) bt full
#0  0x900015e4 in szone_free ()
No symbol table info available.
#1  0x90195edc in CFRunLoopRunSpecific ()
No symbol table info available.
#2  0x927d5f88 in RunCurrentEventLoopInMode ()
No symbol table info available.
#3  0x927dc6f0 in ReceiveNextEventCommon ()
No symbol table info available.
#4  0x9284d7fc in ReceiveNextEventInMode ()
No symbol table info available.
#5  0x03e9051c in wxApp::MacDoOneEvent() ()
No symbol table info available.
#6  0x03e901b0 in wxApp::MainLoop() ()
No symbol table info available.
#7  0x03bc0468 in wxEntry(int&, char**) ()
No symbol table info available.
#8  0x0013b684 in main (argc=1, argv=0xbffffc3c) at amule.cpp:176
No locals.When I quit gdb, amule was still running, but like I said before, not reacting.
Is this enough Info or shall I compile wxWidgets (2.5.2) perhaps also with debug-info?
Also, because this is a OS X bug, is this the right forum to post or shall i post to the OS X forum?
If you need other Info or testruns, just tell me what to do.

Title: Re: backtrace under OS X (Version CVS from 20040927 20:54)
Post by: Kry on September 28, 2004, 07:14:43 PM

This forum is the right place, don't worry.

The bug seems more to be a wxWidgets bug. Too bad.


Do you have any known bugs for Mac? I'm about to release.

Title: Re: backtrace under OS X (Version CVS from 20040927 20:54)
Post by: sssnake on September 28, 2004, 10:58:30 PM

No, no big stuff, if I were you, I would release now :-). Gonna post the little stuff in the OS X forum. I will run amule with gdb from now on, if I have any other backtraces, I'll post them.
cheers

Title: Re: backtrace under OS X (Version CVS from 20040927 20:54)
Post by: phoenix on September 29, 2004, 07:27:57 PM

sssnake,

If you have core files and aMule was compiled with debug information, you can get nice backtraces too, even if you were not running aMule inside gdb.

Cheers!