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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=epY12kLZeZXNp7VJ83CahLO8m0udfcH6oXb1gLS8XA1aRiSOk58iI
	6MGc8e7HwFdSWaTTV+IFj8giumJLOVSNmJFhAk06eBOKY2VsKkobOxUoQvKD2RPM
	f4h1q8MVJWbv8eGN5/Llq4fMgbpsuUguerwDzyHIDoRzhw7lSwwbO4=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Fri, 18 Aug 2017 18:20:40 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: REVISITED: Signal delivered while blocked
Message-ID: <20170818162040.GC6314@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <c05c742f0f3809e6d1afb8fb2c646ad7 AT xs4all DOT nl>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="ghzN8eJ9Qlbqn3iT"
Content-Disposition: inline
In-Reply-To: <c05c742f0f3809e6d1afb8fb2c646ad7@xs4all.nl>
User-Agent: Mutt/1.8.3 (2017-05-23)

--ghzN8eJ9Qlbqn3iT
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Aug 16 23:22, Houder wrote:
> Hi,
>=20
> Please read this post first:
>=20
>     https://cygwin.com/ml/cygwin/2017-08/msg00048.html
>     ( Signal delivered while blocked -- by Noah Misch, August 4th 2017 )
>=20
> This post is not intended to "hijack" the post by Noah Misch; this post o=
nly
> ships an alternative (i.e. revised) testcase for the one by provided by N=
oah
> Misch.
>=20
> The alternative testcase in fact consists of 2 testcases (2 files):
>=20
>  1. sigprocmask-exclusion4.c
>  2. sigprocmask-exclusion5.c

Thanks for the testcases.  This is still a pretty tricky problem and a
few hours of debugging haven't shown anything conclusive.  The signal
code was my former co-maintainer's domain, so I'm not as fluent in
debugging it.

ATM it looks like a race inside of the Cygwin DLL to me.  The checks if
a signal should be handled and the *creation* of the call to the signal
handler (but *not* the actual call to the signal handler) may occur
before the signal is blocked, while the call then occurs after the
blocking.

Anyway, I'm not sure I have enough time to fully immerse into that
problem any time soon.  I'd be not too unhappy if somebody would try to
debug this in the Cygwin DLL, too...


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--ghzN8eJ9Qlbqn3iT
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJZlxPYAAoJEPU2Bp2uRE+g4pMQAIsfJSVWc3kDgM4GgsuDeyPF
/knUHqRvBmAFfFC3glULn65RaSsSOiayVSkpPDysTo7RJZVMPbhe3qiiEFMiI74J
PIsA2uSOOFB7JjQUMtgt+bdffUyWgnvU6TaKDk5GeLRCnBc2vqRHk1XZ+bSfi+1Y
IP1YZBxAt79k3BxEoqi5r9HlFTMQnUFBm26X76QsMrfzYkwwNNOJAGvRZqn/WvJX
tK7DO1tBJgbf2JiaRPc5MCYWKyj7g7ZaVcKGJzAEQpvDMkJcB402Dhqz2euqWx7h
To9/biJDIp5DNXe5H4hU97UoUbNBn3uuwBOzM1AUMrTCpNonS3Mc7EWXttyNQxC0
GIBpgXYx05Oc2em0swUhD0hlYX9vChgV6RcSBbj3hBSOtiddFXP7/70AoK4YCGVR
51KOxzecmPsF8gZz6y2tuL9IJbZ0G/wK9XFx0gvlzuudaK9NBW8UMarJzkRzFHwP
Jsw4TqPhwHuwWYLjbXPXggeas1k83dQoXdHha8ehG1Q/kjkQoTlQpKdbUqRhaWmZ
qqtztCHjCHUXBwD9u2NSi1P0bNA/4ca9sRe2MhW7MkJkihM+iFM7aoY921PHJUJU
t9+jj0Go/wunYgGzDfILhywmliaryL/n09AoMgkK8vlSPADplXN1v1B6kwBj5G1/
zfibscqld2M9SsxohJC5
=W/ev
-----END PGP SIGNATURE-----

--ghzN8eJ9Qlbqn3iT--