Re: Finding out what's incorrectly calling an Obj-C method

Here's where I saw it: Nice blog. Not the first place I've seen this tip but somehow I'd forgotten about it and was delighted to be reminded. --Andy On Mar 4, 2013, at 5:44 PM,

Re: Finding out what's incorrectly calling an Obj-C method

Try breaking on -[NSObject doesNotRecognizeSelector:]. I saw this on a blog somewhere which I will find and credit in a moment. --Andy On Mar 4, 2013, at 4:30 PM, Steve Mills wrote: > On Mar 4, 2013, at 15:17:42, Jens Alfke wrote: > >> IMHO everyone should enable exception breakpoints in all

Re: Finding out what's incorrectly calling an Obj-C method

On Mar 4, 2013, at 15:17:42, Jens Alfke wrote: > IMHO everyone should enable exception breakpoints in all their projects. They > are a life-saver for debugging. Yeah, I usually do, but at times they get in the way because the OS is throwing exception on things I don't care about (usually readi

Re: Finding out what's incorrectly calling an Obj-C method

On Mar 4, 2013, at 1:06 PM, Steve Mills wrote: > 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. It’s an exception, so use the Xcode breakpoints panel to add an all-exce

Re: Finding out what's incorrectly calling an Obj-C method

On Mar 4, 2013, at 14:58:04, Rick Mann 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.

Re: Finding out what's incorrectly calling an Obj-C method

On Mar 4, 2013, at 12:40 , 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