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: Cameron Hayne <email@hidden>
- Date: Sat, 24 Jun 2006 15:45:11 -0400
On 24-Jun-06, at 1:20 PM, Matt Neuburg 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?
EXC_BAD_ACCESS usually indicates a programming error and thus it
isn't something that you usually want to just catch and gloss over. I
would recommend fixing the problem instead. Supply details of why
this is happening in your code and why you can't fix it and maybe we
can help suggest something.
But I think that EXC_BAD_ACCESS will result in a SIGBUS signal. If
so, you could set up a signal handler for SIGBUS and do something
appropriate. See my sample project "TestSignals" (http://hayne.net/
MacDev/TestSignals/) for how to do this and cautions on what is
appropriate in a signal handler.
--
Cameron Hayne
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