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: Jonas Maebe <email@hidden>
- Date: Thu, 17 Aug 2006 16:40:46 +0200
On 17 aug 2006, at 06:45, Scott Ribe wrote:
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.
If all else fails, set a breakpoint on write and put a gdb condition
on it:
b write
cond 1 (char*)strnstr((char*)$r4,"Your error message",$r5) != 0
That's for ppc at least. For Intel, you'd have to figure out where
the arguments are in the write function.
Jonas
_______________________________________________
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