• 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: guard malloc vs dyld
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: guard malloc vs dyld


  • Subject: Re: guard malloc vs dyld
  • From: Dave Payne <email@hidden>
  • Date: Wed, 1 Jun 2005 14:38:19 -0700

On Jun 1, 2005, at 10:33 AM, Stefan Werner wrote:

even with the right Tcl.framework, I still get a SIGTRAP in dyld when
using guard malloc:
This time, it's complaining about a double definition of
_malloc_zone_register, defined in libgmalloc (obviously) and
libSystem.b.dylib. Am I maybe forgetting a linker setting?

Hi Stefan, on your 10.3 system, how are you using Guard Malloc? Are you explicitly setting the DYLD_INSERT_LIBRARIES environment variable in gdb? If so, then you also need to set DYLD_FORCE_FLAT_NAMESPACE to 1. I think that if you're using the Debug --> Enable Guard Malloc menu item in Xcode that it does that for you.


On 10.4 with the associated developer tools, the implementation of Guard Malloc has been changed such that DYLD_FORCE_FLAT_NAMESPACE is no longer necessary. It now works properly with applications that require two-level namespace.


- Dave

_______________________________________________
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: guard malloc vs dyld
      • From: Stefan Werner <email@hidden>
  • Prev by Date: Re: Accelerated Objective-C Dispatch
  • Next by Date: ZeroLink and static libraries
  • Previous by thread: Re: guard malloc vs dyld
  • Next by thread: Re: guard malloc vs dyld
  • Index(es):
    • Date
    • Thread