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

Re: Using MallocDebug


  • Subject: Re: Using MallocDebug
  • From: Michael Rice <email@hidden>
  • Date: Wed, 22 Feb 2006 09:33:00 -0600

Thanks, but that didn't seem to make any difference.

Michael

On Feb 22, 2006, at 2:46 AM, Chris Friesen wrote:

Sounds like you need to set DYLD_FRAMEWORK_PATH to point to the directory that contains the shared library.

-ChrisF

On Feb 21, 2006, at 11:17 PM, Michael Rice wrote:

I'm trying to use the MallocDebug performance tool to track down a memory leak. However, when I try to launch my app, it reports that it can't find some of the dynamic libraries my app depends on. I've tried setting DYLD_LIBRARY_PATH in my ~/.MacOSX/ environment.plist and in my ~/.profile to the appropriate colon- separated list of paths, but that didn't fix the problem. I tried launching MallocDebug both from Finder and from a Terminal that had the correct DYLD_LIBRARY_PATH set, but still no success.

Any thoughts on how to fix this?

Thanks.
Michael


_______________________________________________ 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: 
 >Using MallocDebug (From: Michael Rice <email@hidden>)
 >Re: Using MallocDebug (From: Chris Friesen <email@hidden>)

  • Prev by Date: Re: build failed, no diagnostic messages
  • Next by Date: include problems with XCode and frameworks
  • Previous by thread: Re: Using MallocDebug
  • Next by thread: Re: Using MallocDebug
  • Index(es):
    • Date
    • Thread