Re: trouble using MallocDebug
Re: trouble using MallocDebug
- Subject: Re: trouble using MallocDebug
- From: Dave Payne <email@hidden>
- Date: Mon, 20 Sep 2004 13:38:47 -0700
On Sep 20, 2004, at 1:32 PM, Michael B. Johnson wrote:
ah - that makes perfect sense. I'm debugging an app that's using a
framework from elsewhere that redefines a symbol that I define already
(because this framework is evolving, and earlier versions did not
define this symbol). Since it's a string that actually evaluates to
the same thing, I haven't worried about it.
I'll fix that.
Yep, that would do it.
Also, though, since I much prefer to use Shark for performance
analysis (Shark ROCKS!), I'll take a look at the memory stuff there -
I looked, but didn't see anything.
What I'm trying to do is understand where memory is being allocated in
my app on a particular operation that calls into other folks libraries
as well as my own.
In Shark 4.0, change the "sampling style" popup from Time Profile to
Malloc Trace. You then have to specify a specific process to trace.
Generally, we recommend just doing short sampling runs when doing
malloc sampling with Shark, since it can generate lots of events
quickly.
- Dave
_______________________________________________
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