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; q=dns; s=default; b=w0hO
	Dm/9kkdRO91eEjOdpS8wNUf8UEvrSniLoRoyfzdvbsxFSTBOZKc34cj1DCZ3Cx8L
	HWFtqoZNUkugbElz6VIITp7ZoP8d0WyhPjmHGuHRfUFc57CTt1tROL7Wbnam1vrH
	JnboihOjUjMkXCOyU1xthS9rWIplHsUVNEcMy98=
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; s=default; bh=8nx3rtlPgr
	D7Lq6VD5QzXg6H/7Q=; b=fBsqYvKij5qLqEdFYMGWGlNM+ZhXcXtrevXk/5Xua7
	UrIG8r/reyZKjdMsfsI2T/jVVs0YwnMCjHhC0Qy4K0eEpwfU1mQdy139YvrFolBd
	oIj3jBbeKcrbqLeC3YaKd+OXrHlRAmB1DbY072ohDVOkfGUPYNps2Z4P+1kF2ye7
	k=
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=0.1 required=5.0 tests=BAYES_00,FREEMAIL_FROM,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RHS_DOB autolearn=no version=3.3.2 spammy=
X-HELO: mail-wm0-f48.google.com
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:sender:subject:to:references:from:openpgp         :autocrypt:message-id:date:user-agent:mime-version:in-reply-to;        bh=/cmxdmBvdmcDgm032qtU1FtKnXyzpLTQ8ytwO3AeWsQ=;        b=alidchY4HowIW4JTdmXWLhAmdzYbEG2Z7OQvapSPqK2hkQsZQcZ+/5XuQvS5402GdE         ULjWB524odxx+n3wXwoxgseoDU4VEUmDQd4yjqEgHZl+DH33cyQdLR6XOiVpDyFdDlqh         5rjMkNQoz3MuNjHCcRJ1wQVP3NZ+G0GFMixNmqXx0oF6aUH2Ump3pfhhdxsn6d9u9hz2         xHiuY87TzAs5AFPy5y6ds4QXI4phuMl2Wbj3Iz1KsvAm1jes4fAv4Korw4q5LWop85Ni         EOj7yLyvn1z2JDutvsgy1UO61+70dOCzrSR3ob/KxPJKVn9H6V9HuWPyyUuIYyrdkg/1         py3A==
X-Gm-Message-State: ALQs6tANd+XqOLFbyMoRLQLRLx4bKYO5I+/UYF0G8U35gMgiWwncJnbJ	pQT4lIb1UZBbxGTrUacH+9nD+g==
X-Google-Smtp-Source: AB8JxZoWtWgn4WhnW3KgG/V9gkZn+CAfHhXOq3VNvc0Tmu29s+r2yKPiyoeb5YW52EU+wWV1J2pttw==
X-Received: by 10.167.216.132 with SMTP id u4mr14967665edq.52.1524741174915;        Thu, 26 Apr 2018 04:12:54 -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> <d76cfa4797d30702799a93892d454d95 AT smtp-cloud9 DOT xs4all DOT net> <4a3b47db-fcdb-85f0-ec80-4cffcb7c495a AT users DOT sourceforge DOT net> <26e03635c83cba20a1ef68e238e41ec2 AT smtp-cloud9 DOT xs4all DOT net>
From: Thomas Zimmermann <tdz AT users DOT sourceforge DOT net>
Openpgp: preference=signencrypt
Autocrypt: addr=tdz AT users DOT sourceforge DOT net; prefer-encrypt=mutual; keydata= xsDiBEQ8FzARBAD9199cx5bJZ7nvSuaGA6ZLv1WyPtIeKWXj8mOfpn/tfmKUlzFijUChGBGP 1/FGssV/KnR+1zWdxsgtYuE8bbslJEGRP/fgaOgxisCKjkU8/SKXKKYoxS568m2TwBO512so PTj2mC3yWz4nU7ZTmgoJzf8r8TDZ3GBbHCoO21tUjwCgkjiAm08Kh72NtbMysXW88eOcFfUE ANvt1VrkyDjLD/viv7MHYUMLKLaFdNZUnJi4Rx6NwIqNxLDeGyPPp17/X2ls397Wl9PAZRJB 96/3E5WAOCyaKJc605luoyvv0CJ5+VuAQDVXKGdX/jr7EnhkyXmcm8ChKR/1Lct6jn5Wp922 utdklQcYEkSNMJbRsKReluxXaD6kBAC2qI/mOyRtJLxoszYG2hLf1BAOopJb13J1TCRQv3Df El2zmbPyYOfMQzbnFBrZ5yMve6I5/9hWksMMUWrdtgGDEsBFMa8iFb9FPsbKrDBmR66wpNFf s7GPEcWpIueBGu+vmXtUN8zE4mvUxFixc7iiPx46TCctKFqujGf6ubhlpc0tVGhvbWFzIFpp bW1lcm1hbm4gPHRkekB1c2Vycy5zb3VyY2Vmb3JnZS5uZXQ+wl0EExECAB0FAkQ8FzAGCwkI BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDZ2tfUTvHfCIydAJ4ndgH+dGp131Bx0su0VkWIiCfg iwCdHB339NSWt0kXY4+/Zhfpenzj9EXOwE0ERDwXMRAEAKcJyo9UpIp4Z4Mer58CL+ErcgwU xWdH5yhRV0++D70R6N5e+Yoa20V5trrNhpCEeAvjLW77VRqCYPO3hn0mmN2jSO8qMdBn7rXS ND9WFrlnSSCGsYQeoKj0z2KlQ8Waxg+r3b23azbMinF30x9303S3ZhrWvSf8wxIgd+u3HeXj AAMGA/9s/AWniacRR8T2ABN0ASjXp1SCSYmezL9Jp8MfSWvLcNrB/0Oi/o3+1HfJiTHg7o8l H6tpqScWsKpPZbYxmo9vb9sVjAOLzGpeV8S6Pe1pcXfiOuZLMJ5OTga6GxWimmP7rrWKTIlP x57wXD+v6c4A4VYW973YXNh1mVXwON3ydMJGBBgRAgAGBQJEPBcxAAoJENna19RO8d8IASEA niQqMp4Yd00/t47D09opsugE9GBHAJ9sJZgtyq9lLB3xCFm16nooejR/XA==
Message-ID: <46f53185-1295-e1b8-0121-103f2b7c4f1f@users.sourceforge.net>
Date: Thu, 26 Apr 2018 13:12:53 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <26e03635c83cba20a1ef68e238e41ec2@smtp-cloud9.xs4all.net>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="QuaklEkv47DuYyr07hoBWXn4SpHlbVz0v"
X-IsSubscribed: yes

--QuaklEkv47DuYyr07hoBWXn4SpHlbVz0v
Content-Type: multipart/mixed; boundary="KBKIfBUAKtlvCBOvxcgryUR4gWPBsGY92";
 protected-headers="v1"
From: Thomas Zimmermann <tdz AT users DOT sourceforge DOT net>
To: cygwin AT cygwin DOT com
Message-ID: <46f53185-1295-e1b8-0121-103f2b7c4f1f AT users DOT sourceforge DOT net>
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>
 <26e03635c83cba20a1ef68e238e41ec2 AT smtp-cloud9 DOT xs4all DOT net>
In-Reply-To: <26e03635c83cba20a1ef68e238e41ec2 AT smtp-cloud9 DOT xs4all DOT net>


--KBKIfBUAKtlvCBOvxcgryUR4gWPBsGY92
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

I just saw that the result after returning from a synchronous signal is
undefined. So any behavior seems be OK. I'd still encourage to unify the
behavior of 32-bit and 64-bit code. (See my other mail.)

Best regards
Thomas

Am 26.04.2018 um 13:01 schrieb Houder:
> On Thu, 26 Apr 2018 12:52:54, Thomas Zimmermann wrote:
>=20
>> 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:
>>> =3D20
>>> .. 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.
>=20
> After the invocation of the handler, the program continues with the code
> that attempts 'to divide by zero'.
>=20
> As result of that, the handler is invoked again.
>=20
> Henri
>=20
>> Best regards
>> Thomas
>=20
>=20
> --
> 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
>=20


--=20
Implement thread-safe and fault-tolerant software in C: visit picotm.org
--
GnuPG:          http://tdz.users.sourceforge.net/tdz.asc
Fingerprint:    16FF F599 82F8 E5AA 18C6 5220 D9DA D7D4 4EF1 DF08
Website:        tzimmermann.org


--KBKIfBUAKtlvCBOvxcgryUR4gWPBsGY92--

--QuaklEkv47DuYyr07hoBWXn4SpHlbVz0v
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iF0EARECAB0WIQQW//WZgvjlqhjGUiDZ2tfUTvHfCAUCWuG0NQAKCRDZ2tfUTvHf
CGMHAJ9Cwy0Nx924Qn6aNFmFFm49FEx+LwCffS3LLu0WtgVlKIyPQrHWiQXjuIs=
=pSqa
-----END PGP SIGNATURE-----

--QuaklEkv47DuYyr07hoBWXn4SpHlbVz0v--