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: Rick Mann <email@hidden>
- Date: Mon, 04 Mar 2013 12:58:04 -0800
On Mar 4, 2013, at 12:40 , Steve Mills <email@hidden> wrote:
> I'm seeing some output in Xcode's log:
>
> 2013-03-04 14:35:34.696 Finale 18[15558:303] -[MusicWindowController count]: unrecognized selector sent to instance 0x1bbcd170
>
> I can't find where this is being called from. I've tried implementing a count method, but when I do that it never gets called. I've tried setting symbolic breakpoints on CFShow, NSLog, asl_logv, write, printf, and all sorts of stuff, but either they never stop or the error never gets spit out when those breakpoints are set.
>
> Any other ideas?
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.
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.
--
Rick
_______________________________________________
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