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: Jerry Krinock <email@hidden>
- Date: Sun, 20 Jun 2010 06:13:46 -0700
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.
I'm still working on this, although currently on a slight detour.
Regarding the screenshot in my first post, showing that -[_NSZombie whatever] breakpoints always appear unresolved… Joar said that these breakpoints are unnecessary today. Howevever, if you *do* set one of those breakpoints like I did, is it expected behavior that they appear in Xcode as unresolved?
That seems odd.
_______________________________________________
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