Re: Using MallocDebug
Re: Using MallocDebug
- Subject: Re: Using MallocDebug
- From: David Dunham <email@hidden>
- Date: Wed, 22 Feb 2006 15:43:38 -0800
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.
--
David Dunham A Sharp, LLC
Voice/Fax: 206 783 7404 http://a-sharp.com
Efficiency is intelligent laziness.
_______________________________________________
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