Re: Finding out what's incorrectly calling an Obj-C method
Re: Finding out what's incorrectly calling an Obj-C method
- Subject: Re: Finding out what's incorrectly calling an Obj-C method
- From: Steve Mills <email@hidden>
- Date: Mon, 04 Mar 2013 15:06:03 -0600
On Mar 4, 2013, at 14:58:04, Rick Mann <email@hidden> wrote:
> This sometimes happens to me when something gets released unexpectedly. Try turning on zombies. If that's the case, you'll get a "message sent to deallocated instance" instead.
The object is still very much valid, and zombie detection is on.
> Otherwise, you'll have to look before that call to see what that object is. Clearly, you're treating something as a collection that the runtime thinks is a controller.
It'd really help if I could set a breakpoint on the part of the Obj-C runtime that spits out the "unrecognized selector" error. None of the usual suspects handle that.
--
Steve Mills
office: 952-818-3871
home: 952-401-6255
cell: 612-803-6157
_______________________________________________
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