Re: Seeking advice on debugging "real time" programs.
Re: Seeking advice on debugging "real time" programs.
- Subject: Re: Seeking advice on debugging "real time" programs.
- From: David Dunham <email@hidden>
- Date: Mon, 3 Apr 2006 15:15:27 -0700
On 3 Apr 2006, at 14:19, John Draper wrote:
Using "MallocDebug" is fine when dealing with "not so critical"
timing issues,
but when inside a RTP Thread where timing is everything, these
tools can
slow down the application so much it breaks the timing.
You can find leaks by setting the MallocStackLogging environment
variable, but this does take time (and memory).
I'm still stuck to using X-Code 1.5, so for any new feature
available in the 2.X
series is not going to do me much good.
Why are you stuck?
* Performance testing (Shark), but don't know what I'm looking
for... :-(
But Shark will tell you what you're looking for.
Has anyone on this list come up with an effecive way to identify
and isolate
memory leaks? Is there still hope for me as an X-Code 1.5 user?
Sure, set MallocStackLogging and then use leaks from the command
line. (You'd set a breakpoint at a spot when you expect memory to be
cleaned up -- in my case at the end of main().)
David Dunham http://www.pensee.com/dunham/
Imagination is more important than knowledge. -- Albert Einstein
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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