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:13:11 -0600
On Mar 4, 2013, at 15:03:29, Keary Suska <email@hidden> wrote:
> 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).
Yes, in the debugger. I'll try breaking on all exceptions to see if that helps. Thanks!
--
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden