On Jul 18, 2011, at 05:48, Andre Masse wrote: > -[NSCFString string]: unrecognized selector sent to instance 0x7fff71192b70
I don't think anyone's pointed you in the direction of *reading* this error message. Note that it says -[NSCFString string], not +[NSCFString string]. Someone has sent a 'string' message to a NSString instance. NSString instances don't respond to 'string' messages. NSString *classes* do. That leads me to suspect that you've written some code that accidentally sends the class message to an instance, and that your problem is nothing to do with memory management. The important thing to find out is who is sending the message, not what it's being sent to. > 1- Adding a breakpoint on objc_exception_throw: brings the debugger on > NSApplicationMain... Is this in Xcode 4? Make sure the "level of detail" slider at the bottom of the debugger view in the navigator pane is all the way to the right. If it's in its default middle position, it often collapses the call stack, misleading you to think the exception was in NSApplicationMain (). _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
