• 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 conflicts
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guard malloc conflicts


  • Subject: Re: Guard malloc conflicts
  • From: Chris Friesen <email@hidden>
  • Date: Tue, 14 Jun 2005 13:53:33 -0700

Edit your executable setting in Xcode and add the environment variable 'DYLD_PRINT_LIBRARIES', debug your application then open the console and the last library printed should be the conflicting library.

-ChrisF
PS See the man page for 'dyld' for more options

On Jun 13, 2005, at 9:10 PM, Yves Poissant wrote:

I'd like to enable Guard malloc. But there seems to be a conflict with some redefined symbol based on the "_dyld_multiply_defined_error" proc I get on the stack when it breaks with "Program received signal "SIGTRAP"" status.

I read in the archives that I have to find which library contains which symbol which is redefined. The problem is that I am dealing with a huge application with several libraries.

So, is there a way to figure which symbol might be redefined?

Anybody have experience with this conflict with Guard malloc and would have a hint as to which are the most common conflicted symbols? I would guess the redefined symbol would most probably have to do with memory management. But which symbol?

Thanks,
Yves
_______________________________________________
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


_______________________________________________ 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:
    • Predefined compiler symbols
      • From: Dan Grassi <email@hidden>
References: 
 >Guard malloc conflicts (From: "Yves Poissant" <email@hidden>)

  • Prev by Date: Re: Internal Error Loading Projects After Installing 2.1
  • Next by Date: Problems defining a UTI
  • Previous by thread: Guard malloc conflicts
  • Next by thread: Predefined compiler symbols
  • Index(es):
    • Date
    • Thread