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: Keary Suska <email@hidden>
- Date: Mon, 04 Mar 2013 14:03:29 -0700
On Mar 4, 2013, at 1:40 PM, Steve Mills 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?
Does this happen while you are running the debugger? I get these types of messages from time to time--almost always the -count method being called on something. I expect it has to do with the variable display and inspection. The debugger frequently gets confused in my experience and I would consider them simply noise. Also note that some parts of Cocoa are noisy with exceptions but tend to handle them so they just get logged.
If you are breaking on all exceptions, however, the debugger should break on those as well (as long as you aren't already in it, as I mention).
HTH,
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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