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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=wW4rsJL7vOntziQT
	hHOohEbQJmXe8t0jA4i5cJmayZ1/sIn0qZJGb66zE4p7L3D4X7X9pPI18UiSpKa6
	ryu04qF6Am0EMulgBTbpgSIMCFuEOXFM3KAf3icKTa543hzL+2bvs0NfeeugD4nY
	Z8MezxO3KNr4nQBuWEnSR3MSQPE=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=XQYPHblKJh4NW7ZcBk1Jn0
	bgRpQ=; b=EKwu5sXH0WrNztW1MwoNRUxQQek88ki9C9LCaLAO+5Mts3kysyzqpE
	cCg7Lrd9IP/s7CAIYmSDiktd6qpEktNR1IKDKMy0vn3ZWeFGmIzVD2EyTHUYk+nL
	prG6uaQrOuVM4Om/QbJCgwIMvbITXtvPXvZmGtNxoEaf52ZG4AQ58=
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.4 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy=Best, H*UA:6.1
X-HELO:	mail-wm0-f41.google.com
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=GngZfwUs+lscmQBPZX09s6df5W127B08w8m0j3el0Ow=; b=G9IlQsk64CjOHvnz8Q0IofMgyn0sMpDCzXoIAS/GCfn7A8a3nbBJ6+RJNwzocy/Van buvkqA5cdHsBy7w597mIX5xzEiVTWRoLFr+iA5dn2fNQs/xZ8dwmqEeLW55e7pmDTVW/ DyeoR9EKKB5QXjva+zMfnVPDoiI/ElnM7N3IxVR4XhhClI75BFroKbeiKHJNIQx9eO5n 7c017d6udyyyTwE419/e05zUK0R1WtCeaZId0jrcwtH/zuFjdiPsc8FPmSTCxGZBrVvK /l2mhENr6M0lzJ5KzHJx3vupqvzh5B1vzhFoJd4fljWZrmAvB47FwaLxB+9rzTfCmM6b tKDg==
X-Gm-Message-State:	ALQs6tDs4YqYiuXIWuCzaZGklf47eBzo/9Zycri3Lcw90FVPHLlCqsU3 8+WFzxM9CGIcDWp2RsUOHQbKnAWh
X-Google-Smtp-Source:	AIpwx4+HEiJs3cPCGNGpUQ8DPNwlKAU4VZRWliU0UE/CE7Hd/FHfdCbbQv9yp2pKmvo6NjAiJMkG8Q==
X-Received:	by 10.28.41.130 with SMTP id p124mr17040437wmp.127.1524739476709; Thu, 26 Apr 2018 03:44:36 -0700 (PDT)
Subject:	Re: Bug: Synchronous signals broken on Cygwin 64
To:	cygwin AT cygwin DOT com
References:	<bc993d03-a9ac-d1c9-c33a-03cfc810edbe AT users DOT sourceforge DOT net>
From:	Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID:	<c5ae3eb3-090e-3a3c-64c5-0abfb0b5b477@gmail.com>
Date:	Thu, 26 Apr 2018 12:44:35 +0200
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version:	1.0
In-Reply-To:	<bc993d03-a9ac-d1c9-c33a-03cfc810edbe@users.sourceforge.net>
X-IsSubscribed:	yes

On 4/26/2018 9:57 AM, Thomas Zimmermann wrote:
> Hello mailing list,
> 
> I noticed that synchronous signals (e.g., SIGSEGV, SIGFPE) appear to be
> broken on 64-bit Cygwin systems. I could not find additional information
> on the mailing list. If this is not already a known problem, you'll find
> some analysis below.
> 
> 
> I use Cygwin DLL 2.10 with all packages up-to-date. My test system runs
> Windows 7.
> 
> 
> The expected behavior is that an installed signal handler runs exactly
> once for a signal and the OS terminates the program if the handler
> returns. This works on 32-bit Cygwin. From my observation, Cygwin 64
> differs in the follow ways:
> 
> 1) Generating a synchronous signal on the main thread, makes the signal
> handler enter an endless loop. The attached test 'syncsig.c' illustrates
> this.
> 
> 2) Generating a synchronous signal on an additional POSIX thread ignores
> the installed signal handler entirely. The handler does not run and the
> program gets terminated immediately. The attached test 'syncsig_mt.c'
> illustrates this.
> 
> 
> As mentioned, both cases work correctly on 32-bit installations. I
> cannot point to the exact location of the problem, but it appears that
> the Cygwin exception-handler code is not set up by 64-bit code.
> 
> In case 2) I can see the Windows function KiUserExceptionDispatcher()
> being executed for the synchronous signal on the affected thread. This
> should lead to a call to the Cygwin exception handler. It does for
> 32-bit, but not for 64-bit code.

just for confirmation, same results and discrepancies on my W7

>  From what I've seen, the exception handler is installed in the c'tor
> exception::exception(). [exception.cc:138] The only invocation I found
> was in SetThreadName(). [miscfuncs.cc:951] This set-up code is 32-bit-only.
> 
> 
> BTW, is there a bug tracker for Cygwin? I'd open a bug report there, or
> add the information to an existing one.

there is no bug tracker. Bugs are managed on this mailing list.

> 
> Best regards
> Thomas
> 

Regards
Marco

--
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

- Raw text -