X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=BbBzssWEUq2Hx8d8JlPmiyX3GSUDNigkyTkeoc2v2bN
	uDZBe29U3hUq8TroK/5UQ/csH17UrXCXZEDdI8AccZjqdrLFQP72S1wEGwgGHkoW
	ZEgqqZl89oRGp+98E90t0M7mGybW1UDhhL0z/bNnLG3j9lF6sPc/T953jHzidD2Y
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=sCJaVFXj+cg+4igZ+SWIcPjMyaw=; b=VjJRQUDqVsec2Fakl
	HAcW/mNupPFf0ej99Bs2Tnc2PGqoM4WCfN1zKwBO30gpfG8JRmGTYGZo/K9yT3PE
	ryFZbSiHSKpaX4B4727V/PeMfAF0wysq0BsYb6b6W+1bwqMRRSXRi/HBQNZDpS+k
	R01Psd3Myoyv2PcywswY6vXt7I=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: limerock01.mail.cornell.edu
X-CornellRouted: This message has been Routed already.
Message-ID: <5314C8D3.6000300@cornell.edu>
Date: Mon, 03 Mar 2014 13:24:19 -0500
From: Ken Brown <kbrown AT cornell DOT edu>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Building libsigsegv on Cygwin64
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>
In-Reply-To: <20140303170628.GA7236@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

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
>>> $ ./fault.exe
>>> $ echo $?
>>> 1
>>>
>>> In the 32-bit case, the exit code is 0.
>>>
>>> I don't know if this indicates a Cygwin bug or something wrong with
>>> the test.
>>
>> 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.

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple