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 <smi...@makemusic.com> wrote:

> On Mar 4, 2013, at 15:17:42, Jens Alfke <j...@mooseyard.com> 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 reading print 
> records or some such thing), so they get to be more annoying than helpful. 
> And of course, I can't get this message to fire again now that I have 
> exception breakpoints on. Oh well. I'll stop caring about this...... now.
> 
> And sorry for cross-posting. I incorrectly typed "cocoa" when I meant to type 
> "xcode" when replying to one message.
> 
> --
> Steve Mills
> office: 952-818-3871
> home: 952-401-6255
> cell: 612-803-6157
> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list      (xcode-us...@lists.apple.com)
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/xcode-users/aglee%40mac.com
> 
> This email sent to ag...@mac.com


_______________________________________________

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to