This is the mail archive of the
mailing list for the Cygwin project.
Re: Building libsigsegv on Cygwin64
- From: Ken Brown <kbrown at cornell dot edu>
- To: cygwin at cygwin dot com
- Date: Mon, 03 Mar 2014 13:24:19 -0500
- Subject: Re: Building libsigsegv on Cygwin64
- Authentication-results: sourceware.org; auth=none
- References: <530771A3 dot 7000603 at alice dot it> <53136870 dot 200 at cornell dot edu> <20140303150210 dot GC2469 at calimero dot vinschen dot de> <20140303170628 dot GA7236 at calimero dot vinschen dot de>
On 3/3/2014 12:06 PM, Corinna Vinschen wrote:
On Mar 3 16:02, Corinna Vinschen wrote:
On Mar 2 12:20, Ken Brown wrote:
I found the problem (or at least I found *a* problem): There's a
configure test "checking whether a fault handler according to POSIX
works", which passes on 32-bit Cygwin but fails on 64-bit Cygwin.
I'm attaching a file containing the configure test. Here's what
happens in the 64-bit case:
$ gcc -o fault fault.c
$ echo $?
In the 32-bit case, the exit code is 0.
I don't know if this indicates a Cygwin bug or something wrong with
It indicates a Cygwin bug. Thanks for the report and the testcase.
The joke here is, the signal handler function gets called twice for the
same exception. Proof is that you can remove the second call to crasher
and still sigsegv_handler gets called twice.
I just created a new snapshot which contains the fix. Would you mind
to test it?
It's fixed. Thanks.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple