Re: Weird crash on iOS
Re: Weird crash on iOS
- Subject: Re: Weird crash on iOS
- From: Jens Alfke <email@hidden>
- Date: Wed, 19 Sep 2012 17:09:57 -0700
On Sep 19, 2012, at 3:49 PM, Alex Zavatone < email@hidden> wrote: Actually, when ever a SIGABORT happens, in my case, it generally the result of unrecognized selector sent to instance.
But the OP’s crash wasn’t a SIGABORT, it was a SIGTRAMP (which I’ve barely ever seen before.) That is not the result of an Obj-C exception.
Also, in a message-not-understood exception there are several stack frames of NSObject methods, whose names escape me, dealing with trying to find a method implementation. It’s a very recognizable signature.
And SIGABORT isn’t the significant thing about an exception; it’s just that the runtime panics if it doesn’t find an active @catch farther up the stack, and calls abort(). There are other ways to get SIGABORT, because there are other things that will call abort(), such as malloc’s heap corruption detector. So calling it “a SIGABORT” isn’t a clear description of what’s going on. Call it an “uncaught exception”.
—Jens |
_______________________________________________
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