On Aug 31, 2012, at 9:36 AM, Alex Zavatone <z...@mac.com> wrote: > This reminds me a little of the SIGABRT diatribe that I just wrote about > recently. > It's unrecognized selector sent to instance.
Well yes, but that’s a very common, generic type of crash. Probably ⅓ of the crashes I run into are like that. > You're calling or passing a message that is unimplemented (or misspelled) to > a class instance in your app. OC throws up its arms and bails in this case, > throwing a SIGABRT. In this case it isn’t app code that sent the message, it’s framework code. As Georg pointed out, there is no app code on the stack. That doesn’t necessarily mean it’s a framework bug, but it makes it harder to debug. Setting a breakpoint probably isn’t going to help because there are no accessible variables to inspect. In this case I don’t really have any ideas. If the class of the object being messaged is completely unrelated to the caller or the message (like sending -count to an NSView), that smells like a dealloced-object problem (the address got reused by a completely unrelated object) which can be diagnosed using Zombies. But in this case it seems reasonable for NSDocument to be accessing NSDocumentMoreIVars. It might be a Cocoa bug after all… —Jens _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
