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:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=GMVsPG
	tSgAfaW6k4iDJst1BFBbysqUH/3SpOVTyVrvRowhtLqpNCqn7X1MRfNJLLaSLIbV
	6gJzCNmnytuUIWGXaBAIYevZQwjb5Wtk5wUTJTicZQ9+7uN4XYhQtmF4ug2ww+XH
	icNA2DxA1IAJ5RCndlb03xC65NeGtAkX49sag=
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:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=Az+RVABV9zo9
	WXvSbgIkgujY9pI=; b=jGvVemXdF1MY53MLAUcWfWnF0TGERX7ZouTNgvhImCNY
	KyCjWMuXUq5SEKGKFl4QkiZSa/cb8q6K01gx5FX/RUS/ybquT2+ACCRllMah5HDV
	ufWkfBAAsUnHOEAxFbgk4c8Aad9p+Jwb3ts0HLH0qzKOBuwDegLitnz0ic2lZJo=
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=-2.1 required=5.0 tests=AWL,BAYES_00,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=H*R:D*cygwin.com, H*F:D*nl
X-HELO:	lb2-smtp-cloud9.xs4all.net
Date:	Thu, 26 Apr 2018 12:45:00 +0200
Message-ID:	<d76cfa4797d30702799a93892d454d95@smtp-cloud9.xs4all.net>
From:	Houder <houder AT xs4all DOT nl>
Reply-To:	cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
Subject:	Re: Bug: Synchronous signals broken on Cygwin 64
References:	<bc993d03-a9ac-d1c9-c33a-03cfc810edbe AT users DOT sourceforge DOT net>
In-Reply-to:	<bc993d03-a9ac-d1c9-c33a-03cfc810edbe@users.sourceforge.net>
User-Agent:	mua.awk 0.99
X-CMAE-Envelope:	MS4wfNGcYhKwFsBJtQlO1X0H50BRsEcYI3QJFQMGR3elQTNQzr3S+DheqrArjFh194yIDc9P2zhgZRLStN6pHi+aDnOPG1dAG6PvJrnGMQ9rIUv68gj1rbnj uHIP/ZMqni851w07FoL3frBj+mB0x5/eOkcO7lKEY/oejbhcmTQgKX5dAjHJpL4tE5lRJrg8P7kDmw==

On Thu, 26 Apr 2018 09:57:59, 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:

.. uhm, unless SA_RESETHAND (sa_flags) has been specified, I expect the
handler to be invoked again and again ...

And that is what I observe on Linux ...

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

Yes, this behaviour is wrong ...

Henri


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