Re: can I catch an EXC_BAD_ACCESS?
Re: can I catch an EXC_BAD_ACCESS?
- Subject: Re: can I catch an EXC_BAD_ACCESS?
- From: "Peter CK" <email@hidden>
- Date: Sun, 25 Jun 2006 00:46:34 -0400
I've had a similar experience. Although in my case, EXC_BAD_ACCESS means that I have to kill x-code and restart my machine. Everything freezes up and the same thing happens again unless I restart. No call stack, no nothin, just craps on me. It might be because I'm using xcode
2.2, but I am quite certain that X-code does not handle this type of error very gracefully.
Matt, what type of bug did you find in your code that was causing EXC_BAD_ACCESS ?
Peter
On 6/24/06, Matt Neuburg <email@hidden> wrote:
Under certain conditions (out of my control) my app gets an EXC_BAD_ACCESS.
I know where this is happening and have wrapped that part of the code in a
@try/@catch but it doesn't help: the program stops dead and the @catch stuff
never runs. Is there a way to catch this sort of thing?
Also: In Xcode, when this happens, I fall into the debugger window. I would
prefer instead to have the app crash so that I can see what the end user
would see. How can I arrange for that?
Thanks. m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/
>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden
email@hidden
_______________________________________________
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