From: Olivier K. <ka...@ka...> - 2004-08-04 11:32:37
|
Hi, I just got the following message sending a small text in an MSN chat conversation, and would like to track it down; *** malloc[12164]: Deallocation of a pointer not malloced: 0x2; 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 debug can someone tell me the way I can proceed ? I heard of valgrind which seems to be one of the best tool for i386 (linux ppc supported too), but I have no idea on what to use with osx ... Olivier |
From: Mark D. <ma...@ki...> - 2004-08-05 15:31:08
|
On Wed, 4 Aug 2004 13:32:27 +0200 (CEST), Olivier Kaloudoff wrote > Hi, > > I just got the following message sending a small text in an MSN > chat conversation, and would like to track it down; > > *** malloc[12164]: Deallocation of a pointer not malloced: 0x2; 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 > debug > > can someone tell me the way I can proceed ? I heard of valgrind > which seems to be one of the best tool for i386 (linux ppc supported > too), but I have no idea on what to use with osx ... > > Olivier On x86 Linux, setting the environmental variable MALLOC_CHECK_=2 is often useful in debugging problems freeing memory. I don't know if that would be helpful, or if it works for osx. You can try looking at the Notes at the bottom of the malloc man page to see if it's supported. -Mark -- O O Mark Doliner \ | ma...@ki... \ | www.kingant.net "There needs to be a better word for weird." |
From: Nathan C. <co...@bu...> - 2004-08-05 16:18:34
|
Hi, I'm pretty sure that recent versions of Xcode come with a utility called dmalloc. It might be helpful, but I don't expect it to nearly as much as valgrind. For example, I doubt that it can catch writes to freed memory. -Nathan On Thu, Aug 05, 2004 at 10:30:15AM -0500, Mark Doliner wrote: > On Wed, 4 Aug 2004 13:32:27 +0200 (CEST), Olivier Kaloudoff wrote > > Hi, > >=20 > > I just got the following message sending a small text in an MSN > > chat conversation, and would like to track it down; > >=20 > > *** malloc[12164]: Deallocation of a pointer not malloced: 0x2; This=20 > > could be a double free(), or free() called with the middle of an alloca= ted > > block; Try setting environment variable MallocHelp to see tools to help > > debug > >=20 > > can someone tell me the way I can proceed ? I heard of valgrind > > which seems to be one of the best tool for i386 (linux ppc supported=20 > > too), but I have no idea on what to use with osx ... > >=20 > > Olivier >=20 > On x86 Linux, setting the environmental variable MALLOC_CHECK_=3D2 is oft= en > useful in debugging problems freeing memory. I don't know if that would = be > helpful, or if it works for osx. You can try looking at the Notes at the > bottom of the malloc man page to see if it's supported. > -Mark |
From: Evan S. <ev...@dr...> - 2004-08-05 17:12:57
|
I would recommend reading http://developer.apple.com/releasenotes/DeveloperTools/ MallocOptions.html which explains all the malloc debugging options available on OS X. Setting MallocStackLogging to 1 is the most important step, like the MALLOC_CHECK_ Mark mentioned; the other options may be of use for you, as well. -Evan On Aug 5, 2004, at 10:30 AM, Mark Doliner wrote: > On Wed, 4 Aug 2004 13:32:27 +0200 (CEST), Olivier Kaloudoff wrote >> Hi, >> >> I just got the following message sending a small text in an MSN >> chat conversation, and would like to track it down; >> >> *** malloc[12164]: Deallocation of a pointer not malloced: 0x2; 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 >> debug >> >> can someone tell me the way I can proceed ? I heard of valgrind >> which seems to be one of the best tool for i386 (linux ppc supported >> too), but I have no idea on what to use with osx ... >> >> Olivier > > On x86 Linux, setting the environmental variable MALLOC_CHECK_=2 is > often > useful in debugging problems freeing memory. I don't know if that > would be > helpful, or if it works for osx. You can try looking at the Notes at > the > bottom of the malloc man page to see if it's supported. > -Mark > > -- > O O Mark Doliner > \ | ma...@ki... > \ | www.kingant.net > "There needs to be a better word for weird." > > > > ------------------------------------------------------- > This SF.Net email is sponsored by OSTG. Have you noticed the changes on > Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, > one more big change to announce. We are now OSTG- Open Source > Technology > Group. Come see the changes on the new OSTG site. www.ostg.com > _______________________________________________ > Gaim-devel mailing list > Gai...@li... > https://lists.sourceforge.net/lists/listinfo/gaim-devel > |