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=KFCUyGwecrPfEC0QmVsvFHqvD3FI016B6u4P41MbKRUixFNfcZdOo
	tb6Sp3AhDCn6ebcXquCZuatfmRtXYlTSlmh0gec5loc0EdkpbmZE/nkOgnJGKyDY
	qtyebjGIbXPw0YTpCpsWZvtmb005XW3vbJptYQJRzJ99wpNJjOCn/s=
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=MDFdaVD6nasWltGsznXXQ6Hse5Y=; b=rMiRc3oJUGbUcBk2KJoiI2otc0jU
	J7K7c27pQj4Ix/Xf8py+sWupK3iGOI3hbntMq3UtDDDjTciks3bfMY/X/q4LIO2Z
	EMVmjZkFfgIp0dfxswAQi2clDH/6AIzzwZjHm8+PcmALutk0H7EJmlx97/D2tX5Q
	u5Lzz+8GYq+24Lk=
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:58:44 +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:	<20151105175844.GC20857@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> <20151105175546 DOT GB20857 AT calimero DOT vinschen DOT de>
MIME-Version:	1.0
In-Reply-To:	<20151105175546.GB20857@calimero.vinschen.de>
User-Agent:	Mutt/1.5.23 (2014-03-12)

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

On Nov  5 18:55, Corinna Vinschen wrote:
> 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 t=
he
> > > > parent resumes and finishes the test loop alright and it can be
> > > > interrupted again from the shell.  The hang happens after the first=
 test
> > > > succeeds in both the parent and child.
> > >=20
> > > I have just managed to kill the parent (returning the shell prompt) a=
nd
> > > 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?
>=20
> 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.
>=20
> 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.
>=20
> I (hopefully) fixed the issue and uploaded yet another developer
> snapshot to https://cygwin.com/snapshots/ (with ACL changes again).

Hang on for a while, I forgot to push the changes upstream before
creating the snapshot.  Try in half an hour or so.


Sorry,
Corinna

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

--7qSK/uQB79J36Y4o
Content-Type: application/pgp-signature

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

iQIcBAEBCAAGBQJWO5jUAAoJEPU2Bp2uRE+gc5kP+wSjmNzdN8w6JjGGT6p+a4wM
jloeIp2SfFssInVn2wP2PqQinMOoNO4armG7utF6r9FPcgWIexnZvcMRhA7mPnek
pOuZAojLDL0OqGii0fheTWm1xIyos7iS19If/xKmFmlslUMsMm72GMCoeINJw+Io
2ZpyqZIaj6HMlo6bjgboH0zVBW5TAI79I77PjA0kiNoSxqvUREPycBwn7467jSJp
3VFHSO0y8Dc9jXajrDVSh/0SVw1ZUzb1n+M5JQUjyaihx0vVdPb6gVOSPgfwPh5T
4TsRUInpMEeDH6bQ8Ztu5dfuaoZdnzjIuLuDetAhHXAlyBszi7zdl+4mG0BwfmIr
QAwNcLsWat4+1y4VptVEBQlmGpFttqQh2hoNThMc1qdQRp5Np1ZXEglkbZdvdrFA
RYbz5Ksfs1lwF8DJh9gQOx+ZFnJicmd8fceOm7iY8I0AxpTLnyt1rKKQMkEz42HY
U02oZFJKFxWe+paLEeYb5lChUN304G/BVZTPKTau8kdOvZBaOEVe6JyDcItsXCXU
+vyTGj1DjhVsCqWWjocXqvgH/VQesea5hRHZgI+OhIPKZ0uHMsYk39AJMH/apC8h
sYOnwUxFwILgwdkKWkXbHMUPvLdclcwMLfcwiUcDJEK+dqBzZCNEPJkgdWj/7dbc
jcFlRJV2ANLal293T5NW
=kP2v
-----END PGP SIGNATURE-----

--7qSK/uQB79J36Y4o--

- Raw text -