This is the mail archive of the
mailing list for the Cygwin project.
Re: 2nd occurrence of signal not being handled?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sat, 19 Dec 2009 13:03:22 -0500
- Subject: Re: 2nd occurrence of signal not being handled?
- References: <loom.20091219T060807email@example.com>
- Reply-to: cygwin at cygwin dot com
On Sat, Dec 19, 2009 at 05:23:42AM +0000, Mark Geisert wrote:
>I'm trying to get a larger application working but have an issue with
>signal handling. I've boiled the issue down to the STC below. It
>causes two access violations, only the first of which gets handled by
>the SIGSEGV signal handler I've registered for the purpose. The second
>access violation kills the program, as if the handler were no longer
>registered. Using diagnostic code not shown I've made sure the handler
>is still registered, but somehow it's not being called by Cygwin's
>internal fault handling. Or maybe there's some subtle mistake in my
>use of the signal functions. Any advice would be appreciated.
I don't suppose you tried it on linux? Cygwin behaves the same way as
linux. There may be some sa_flags setting that will cause the handler
to continue to be arms.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple