• 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 problem freeing strdup strings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory problem freeing strdup strings


  • Subject: Re: Memory problem freeing strdup strings
  • From: Allen Cronce <email@hidden>
  • Date: Fri, 02 Mar 2007 09:50:39 -0800

Thanks for the response Eric.

Eric Albert wrote:
> It looks like you're linking against libMallocDebug.a.  Don't do
> that.  (We shouldn't even ship the .a.)  Instead, just launch your
> application with the MallocDebug application.  That'll work properly
> with strdup and other functions inside Libc which call malloc.
Yes, this happened with the -lMallocDebug "other linker" flag. The
thinking was that it would be good to have this on at the project level
for some of our debug targets.

Maybe you can use my radar bug as a reminder to remove or fix
libMallocDebug.a.

Best,

--
Allen Cronce
 _______________________________________________
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

References: 
 >Memory problem freeing strdup strings (From: Allen Cronce <email@hidden>)
 >Re: Memory problem freeing strdup strings (From: Eric Albert <email@hidden>)

  • Prev by Date: Re: Memory problem freeing strdup strings
  • Next by Date: Mystery compilation errors: /.fseventsd/ppc/types.h: Permission denied
  • Previous by thread: Re: Memory problem freeing strdup strings
  • Next by thread: Mystery compilation errors: /.fseventsd/ppc/types.h: Permission denied
  • Index(es):
    • Date
    • Thread