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=MBnkvx
	HCN3Dji6iVSr0nNC8oBwkvJzBFWRhrOb9DifRtk/FMnYvb8pH73UCm+Ed8wNMIiE
	yeBWwn9sPtGu9IjtaHbtAQKIaqd5JGoRGLgMqvt7SnypprhLQVPsP6nuySeLgnZy
	+MHokKyhOQGFHSPGyNkQeRyXqynRTUdOfZb8A=
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=bPy8qm0j29OH
	oDrdQ2RELXH6um8=; b=DOnx79lpwY7140oOkr37xmx5EA2AkR26dxST5XTQ3P1u
	7rSmwL087Ta2ybSAFkvjZXYUuUL9uqmn4a/3/rN7ItapK/28KWVkjfnd8USK+8Ca
	2xeD/V+ZLA6ysTaGHBO+SR/T56Yy194WaruJogEbrBMt+uSqp1Ksf7Ca1/1uazY=
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=recalled, Best
X-HELO:	lb2-smtp-cloud9.xs4all.net
Date:	Thu, 26 Apr 2018 13:01:59 +0200
Message-ID:	<26e03635c83cba20a1ef68e238e41ec2@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> <d76cfa4797d30702799a93892d454d95 AT smtp-cloud9 DOT xs4all DOT net> <4a3b47db-fcdb-85f0-ec80-4cffcb7c495a AT users DOT sourceforge DOT net>
In-Reply-to:	<4a3b47db-fcdb-85f0-ec80-4cffcb7c495a@users.sourceforge.net>
User-Agent:	mua.awk 0.99
X-CMAE-Envelope:	MS4wfOgaUrCklKxJDo/c6wxeuK4sg3VoU9EQS4h0YrJJB3XzaSvhxgelA7eORV3Mkn796R3ToW90bLv4fTSipKnGp0imRUGj7snVxfI4MTBbKeaEpICra2tI rOn4rUvQBLinHEcIVsx4KTtizLQLhQrNgYTOVlh2Gm40aB0aiWWqNhdjF2xHrd/AiAIVDEtAJl72qg==

On Thu, 26 Apr 2018 12:52:54, Thomas Zimmermann wrote:

> Hi
> 
> Am 26.04.2018 um 12:45 schrieb Houder:
> >> 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:
> >=20
> > .. uhm, unless SA_RESETHAND (sa_flags) has been specified, I expect the
> > handler to be invoked again and again ...
> 
> What I mean is that the installed signal handler is re-called constantly
> for the same HW exception (div-by-zero in this case). It is as if
> there's an endless loop around the signal-handler function.

After the invocation of the handler, the program continues with the code
that attempts 'to divide by zero'.

As result of that, the handler is invoked again.

Henri

> Best regards
> Thomas


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