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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=amvUby9g2DL/Ag5cKxj2oihpTgGcrX/MnYjzkJ1Toa9CjQ77iff/P
	dn5G1l1J5eDOKAIusgEG5PzCHjkuqRpOXcZj6N2dpa5rryLjW70C1UUB0LxhPvLz
	oOixTZHx6aQupDcnDdDiR/38GXdw/wYe42cZwEGccjOemL0Cs3FvKM=
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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=z3c4xHSOpy4voZEUsxecRv6D3bQ=; b=lpPEP+g6pFTGjY8j0+DhsZdOUxps
	NzxylL1NAu+86QgP3rdav6VJlLQCQFXWjeoS+G6r4fZ0Rp3bJyUKCWbs1d1CspAi
	YIH1/7tjwYhoC2mK9FHg0SMy+t5QVkMYaY+V6B1x115IXJaqLIBvJmU26pdX6FQS
	jcIgp49JK5MBfA4=
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=-5.4 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Thu, 5 Nov 2015 18:55:46 +0100
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.6
Message-ID:	<20151105175546.GB20857@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<announce DOT 20151104091229 DOT GB21525 AT calimero DOT vinschen DOT de> <87pozpwrao DOT fsf AT Rainer DOT invalid> <87bnb9wk11 DOT fsf AT Rainer DOT invalid> <877flxwj6z DOT fsf AT Rainer DOT invalid> <20151105092448 DOT GC18221 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20151105092448.GC18221@calimero.vinschen.de>
User-Agent:	Mutt/1.5.23 (2014-03-12)

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

On Nov  5 10:24, Corinna Vinschen wrote:
> On Nov  4 22:25, Achim Gratz wrote:
> > Achim Gratz writes:
> > > Just confirmed this on another system.  If I kill the child, then the
> > > parent resumes and finishes the test loop alright and it can be
> > > interrupted again from the shell.  The hang happens after the first t=
est
> > > succeeds in both the parent and child.
> >=20
> > I have just managed to kill the parent (returning the shell prompt) and
> > have the child complete the test loop output to the terminal.  So I
> > guess the communication ping-pong is somehow buggered up so that pipes
> > start blocking.
>=20
> Staring into the latest version of my new function to remove pending
> signals, after having some *more* coffee, it seems pretty clear I
> screwed this up nicely.
>=20
> What I was missing all the time was to iterate over the list of pending
> signals if there's a pending signal which doesn't have to be cleared.
> This case was just missing.  Duh!  I guess I didn't really cover myself
> in glory here...
>=20
> I applied yet another patch and uploaded a new developer snapshot
> (this time *with* the ACL changes) to https://cygwin.com/snapshots/
>=20
> Can you please give it a try ASAP?

For the records, I got a testcase from Achim to reproduce the issue
which, incidentally, is still present in that snapshot.  It turned out
that the problem Achim was reporting has nothing to do with the new code
clearing pending signals.  It was a completely different bug, which just
showed another behaviour due to the signal change.

In fact what happened was a deadlock when parent and child process
were industriously trying to lock a file using flock(2).  This must
have been present for a long time, in fact.

I (hopefully) fixed the issue and uploaded yet another developer
snapshot to https://cygwin.com/snapshots/ (with ACL changes again).

New test release follows soon.

Achim, thanks for the report and the testcase.


Corinna

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

--jq0ap7NbKX2Kqbes
Content-Type: application/pgp-signature

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

iQIcBAEBCAAGBQJWO5giAAoJEPU2Bp2uRE+gPT4P/3H9XLuktRb+VBrLzttMz9Zw
qKgrLrON9+dv0IRS5XVJTR66lbcW1Mo1wYM9JGn2iuzCn0OkKXl/V5Stk6u7MwtE
KvkvoQytzi4thfrZyJjrAHvZdfBC18SpPpXtGpX7cqmI/jNn6OQOQJ1IbjtcJd+K
0dmL5WSWk/6N+NJx13w/d3U9Ci0+tikFTV9MrVrXFRHM2eHuFpMY7bmmr6jBlJox
um1m11z3RV7eaROGHEhCInhlI+6gBWPb9TrRLpLBYXqagRtp3AoWYlxTc2oTqBzB
xS4+OI+qLoSqBLnQtLfeqOWcT9fWeAdlAsp5ZwmBCL717ZtdWymNGiLc8GGueFSD
u/4idEE9nOlavMnClaYuInDMl+T1ogTZcKozGYEXehekyW1TeJBFdxXz71NQuzhJ
oriK0MzQdlHaf4Jp9YPSm7fXiUMQ21Kf6VTePVCM4Zm1GGRcEIh+PMY1uBijAo4j
/cXGNQ9znaNmAauXjP/dFuFc5HZAk+h7ZP2UzQlL2qkroRel0upbTdngndLIZ70V
LSqwr3r2jM0Xmvp05v41nhDO6p403yC59zyZcGpgHybr6Bq1AsbaZR/NK82nnu5O
/YTg/MePWVAulmpF/Jn/TubsHTxkNheufcbZwX4KbCijQynv4dV2vkUATAQgYZEt
sc/Vmc86FfZ8QOaQHT4M
=v+Xp
-----END PGP SIGNATURE-----

--jq0ap7NbKX2Kqbes--

- Raw text -