• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Finding out what's incorrectly calling an Obj-C method
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • Subject: Re: Finding out what's incorrectly calling an Obj-C method
  • From: Andy Lee <email@hidden>
  • Date: Mon, 04 Mar 2013 17:47:42 -0500

Here's where I saw it:

<http://www.fruitstandsoftware.com/blog/2012/08/quick-and-easy-debugging-of-unrecognized-selector-sent-to-instance/>

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, Andy Lee <email@hidden> wrote:

> 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 <email@hidden> wrote:
>
>> 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
>>
>>
>>
>> _______________________________________________
>> 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
>
>
> _______________________________________________
>
> 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


 _______________________________________________
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

References: 
 >Finding out what's incorrectly calling an Obj-C method (From: Steve Mills <email@hidden>)
 >Re: Finding out what's incorrectly calling an Obj-C method (From: Steve Mills <email@hidden>)
 >Re: Finding out what's incorrectly calling an Obj-C method (From: Andy Lee <email@hidden>)

  • Prev by Date: Re: Finding out what's incorrectly calling an Obj-C method
  • Next by Date: Re: Xcode 4.6 leaves unsupported attribute in xib files even after turned off?
  • Previous by thread: Re: Finding out what's incorrectly calling an Obj-C method
  • Next by thread: OT: MBP Support for Core i5/i7 rdrand instruction?
  • Index(es):
    • Date
    • Thread