• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Memory debugging problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory debugging problems


  • Subject: Re: Memory debugging problems
  • From: Eric Albert <email@hidden>
  • Date: Fri, 21 Oct 2005 17:59:44 -0700

On Oct 21, 2005, at 1:03 PM, Mark Wagner wrote:

My program has a problems: it crashes with an access fault somewhere
in malloc() -- most likely a memory corruption issue.  I can't seem to
use any of the memory debugging tools to track this down, though.
Trying to use GuardMalloc causes the program to crash with the
following errors:

dyld: /DEVELOPMENT
xcode/TGEQ/TGEQ.prj/build/TGEQ-macho.app/Contents/MacOS/TGEQ-macho
multiple definitions of symbol _malloc_jumpstart
/usr/lib/libgmalloc.dylib(single module) definition of _malloc_jumpstart
/usr/lib/libSystem.B.dylib(scalable_malloc.So) definition of _malloc_jumpstart

With MallocDebug, it crashes while starting up, and the crash log
shows the same basic error of multiple definitions of
_malloc_jumpstart.  How can I fix this?  I'm using XCode 1.5 (gcc 3.3)
on MacOS 10.3.9.

Try Tiger. We fixed things there so conflicting symbols no longer cause Guard Malloc to not run.


Hope this helps,
Eric

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: Memory debugging problems
      • From: Mark Wagner <email@hidden>
References: 
 >Memory debugging problems (From: Mark Wagner <email@hidden>)

  • Prev by Date: Re: Proper address for Xcode feedback
  • Next by Date: Re: static libraries
  • Previous by thread: Memory debugging problems
  • Next by thread: Re: Memory debugging problems
  • Index(es):
    • Date
    • Thread