Re: How exactly are we supposed to debug memory problems???
Re: How exactly are we supposed to debug memory problems???
- Subject: Re: How exactly are we supposed to debug memory problems???
- From: "Sean McBride" <email@hidden>
- Date: Thu, 17 Aug 2006 13:23:40 -0400
- Organization: Rogue Research
On 2006-08-16 22:45, Scott Ribe said:
>I've got a double free. MallocBadFreeAbort doesn't abort. Setting a break in
>szone_error doesn't do anything either. Setting a break in malloc_printf
>does work, but that's mostly useless to me because I also need to use
>MallocCheckHeapStart & Each.
Jonas' workaround is great, but you may also want to look at this old thread:
<http://lists.apple.com/archives/xcode-users/2005/Sep/msg00668.html>
And BTW, you seem to be right about MallocBadFreeAbort, I just tried in
a test app, and it definitely does not work.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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