ECX_BAD_ACCESS again
ECX_BAD_ACCESS again
- Subject: ECX_BAD_ACCESS again
- From: Robert Bielik <email@hidden>
- Date: Sat, 05 Jan 2008 12:00:32 +0100
Hi all,
I've been searching the lists here with a fine-tooth comb, but have not
found one adequate explanation on how to handle EXC_BAD_ACCESS exceptions.
My problem: I'm developing a cross platform appl, where I'm using a
third-party library which occasionally throws a EXC_BAD_ACCESS. I don't
have the source code for the library, and I have NO choice but to use
that particular library. In other words I have no choice but to handle
the EXC_BAD_ACCESS.
The problem occurs in Windows too (with the windows version of the
library), but there I can use set_se_translator to translate the SE to a
normal C++ exception.
Is there no way to do something similar in Mac OS X? I.e. just to handle
the exception and to move on.
TIA
/R
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden