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:30:11 -0600
On Mar 4, 2013, at 15:17:42, Jens Alfke <email@hidden> 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
_______________________________________________
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