EXC_BAD_ACCESS instead of SIGSEGV?
EXC_BAD_ACCESS instead of SIGSEGV?
- Subject: EXC_BAD_ACCESS instead of SIGSEGV?
- From: Simon Gray <email@hidden>
- Date: Thu, 6 Nov 2003 12:59:41 +0000
Good morning all,
I wonder whether someone could point me in the right direction for this
problem.
I'm working with the GNU libsigsegv library
(
http://sourceforge.net/projects/libsigsegv/) as I'm doing some
investigative work on page-mapping in Mac OSX 10.3 and I've run into a
problem:
The basic configure script tests signal handling via the code below but
no longer works in 10.3 as
a GDB trace shows that an EXC_BAD_ACCESS is generated instead of
SIGSEGV in the
function "crasher()",
and it doesn't seem possible to install a signal handler for
EXC_BAD_ACCESS (unsurprisingly, as its not a BSD signal).
Inexperienced as I am with Mach, I'm really not sure the best approach
to resolving this issue - any pointers?
best regards
Simon Gray
PS I would have attached the code below but it goes over the 8K limit :(
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.