Re: _NSZombie Breakpoints don't Resolve (Xcode 3.2.2)
Re: _NSZombie Breakpoints don't Resolve (Xcode 3.2.2)
- Subject: Re: _NSZombie Breakpoints don't Resolve (Xcode 3.2.2)
- From: Ken Thomases <email@hidden>
- Date: Sun, 20 Jun 2010 08:47:43 -0500
On Jun 20, 2010, at 8:13 AM, Jerry Krinock wrote:
> On 2010 Jun 20, at 03:03, Paul Sanders wrote:
>
>> Have you tried setting breakpoints on malloc_error_break and objc_exception_throw? You can do this from the debugger console window (with the 'b' command) and doing so will not change the behaviour of your application in the way that enabling zombies does.
>
> Thank you, Paul. Yes, I have set those breakpoints and, depending on how the crash occurs, sometimes they break. But, in my brain, that doesn't allow me to identify the dead object which received the message or whatever, since it's already been overwritten. Hence enabling zombies.
You want MallocStackLoggingNoCompact (not quite the same thing as MallocScribble). Then, when you get a crash or hit a breakpoint, identify the address that's causing the trouble and use gdb's info malloc-history command, or the malloc_history standalone program.
Also, to me, this:
> malloc: *** error for pointer being freed was not allocated, selector sent to object that doesn't recognize it
does not suggest a zombie, which is why I don't expect NSZombie to catch it. If the pointer was not allocated, that's different from having already been freed. I think you have a garbage pointer, not a pointer to a deallocated object.
Regards,
Ken
_______________________________________________
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