Re: Using MallocDebug
Re: Using MallocDebug
- Subject: Re: Using MallocDebug
- From: Michael Rice <email@hidden>
- Date: Wed, 22 Feb 2006 20:55:58 -0600
On Feb 22, 2006, at 5:43 PM, David Dunham wrote:
Michael
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?
You might not actually need MallocDebug. If you add
MallocStackLogging as an environment variable (to your executable's
info), then you can run the leaks command line tool.
Thanks, that does work - the output is a bit cumbersome to sift
through. I noticed someone else mentioned the "Launch Using
Performance Tool->MallocDebug" menu option. This works, since I'm
able to set the environment variables for my app in the Xcode
project. Now for the hard part - tracking down the leak.
Thanks again.
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