Re: -[_NSZombie methodSignatureForSelector:] not working
Re: -[_NSZombie methodSignatureForSelector:] not working
- Subject: Re: -[_NSZombie methodSignatureForSelector:] not working
- From: "Michael Ash" <email@hidden>
- Date: Thu, 30 Oct 2008 14:16:08 -0400
On Thu, Oct 30, 2008 at 1:41 PM, Chris Kane <email@hidden> wrote:
> As long as you don't foolishly have a signal handler for SIGTRAP setup to
> ignore it, the zombie mechanism causes its own debugger trap for you in 10.5
> and later. For stopping in the debugger purposes, no breakpoint is needed.
> If you have a SIGTRAP handler, it will get called instead of a debugger
> trap, and you can break on your handler.
Thank you very much for the information. It seems that the technote
needs to be updated, but this is not such a big deal if it will break
in the debugger automatically. I'll file a bug on it.
What prompted the original question, though, was that my debugger was
*not* stopping. Of course when I test it now it stops fine. But before
I saw several zombie messages logged over the space of a few minutes
before another exception (the NSOperation exception I posted about in
another message) brought things down.
Perhaps this should go over to the xcode-users list, but since you
mentioned it, what could cause me to foolishly ignore SIGTRAP? I don't
have any signal handlers installed in the program in question, and a
quick test of messaging a released object at the top of main() breaks
into the debugger correctly, as do tests in a couple of other
locations I tried. Maybe I just imagined the previous difficulty....
In any case, thanks again for the information, it's good to know how this works.
Mike
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden