On Fri, Jan 22, 2010 at 6:10 AM, Alexander Bokovikov <openwo...@uralweb.ru> wrote: > Browsing the console log I've found that my app raises an exception, when it > is launched in Mac OS X 10.4. I built it in 10.5 with 10.4 as a target > setting. I didn't see any problems there. The exception is caused by > unsupported selector calling [NSString boolValue]. I've scanned all my > project but couldn't find any reference to "boolValue". What could cause the > problem?
Unrecognized selector exceptions are usually caused by memory management bugs. It looks like an NSNumber is getting overreleased somewhere, and its memory is being taken up by an NSString. Since you don't do any -boolValue calls yourself, Keary's thought about bindings is probably correct. You should turn on zombies and run your app in the debugger on 10.4. --Kyle Sluder _______________________________________________ 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
