Re: troubleshooting unrecognised selector messages

  • On 07.11.2007, at 22:21, Andrew Ebling wrote:

    > 2007-11-07 21:15:35.692 RaiseMan[543:10b] *** -[NSCFNumber <null
    > selector>]: unrecognized selector sent to instance 0x110e50
    >
    > Any ideas how to go about troubleshooting these sorts of messages?
    > I tried poking around with gdb on the command line to see if I could
    > find out what was sitting at the supplied address, without success.

    The easiest way to debug such behavior is to provide the unrecognized
    method in a category and set a breakpoint there.
    A little more effort is to add a category for -
    (void)doesNotRecognizeSelector:(SEL)aSelector, either for the
    concretete class that throws or up in the class hierachy to NSObject.

    Just make sure either version is not present in release builds.
previous month november 2007 next month
MTWTFSS
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    
Go to today