From:	khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject:	catching SIGSEGV
31 Dec 1998 10:20:22 -0800 :
Message-ID:	<199812311805.MAA29176.cygnus.cygwin32.developers@modi.xraylith.wisc.edu>
To:	cygwin32-developers AT cygnus DOT com

I've been catching up on various Cygwin GCC related bug reports, and lots
of those have the usual complaint -- GCC died with a win32 window saying
some about a page fault. Basically, all of these can be traced to the fact
that cc1plus (or cc1) segfaulted and the signal handler that allows GCC to 
die gracefully didn't get called. 

There is a comment in GCC about Cygwin not being able to catch SIGSEGV,
and my test code shows that the behaviour is still true. What needs
to be done to fix this? Also, how come GDB can catch it (of course then
GDB can't pass it to the child, but that's a different issue)?

Regards,
Mumit

- Raw text -