From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 89975 invoked by alias); 5 Nov 2015 09:24:52 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 89940 invoked by uid 89); 5 Nov 2015 09:24:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.5 required=5.0 tests=AWL,BAYES_20,KAM_LAZY_DOMAIN_SECURITY autolearn=no version=3.3.2 X-HELO: calimero.vinschen.de Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 05 Nov 2015 09:24:51 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 52E3DA805F6; Thu, 5 Nov 2015 10:24:48 +0100 (CET) Date: Thu, 05 Nov 2015 09:24:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.6 Message-ID: <20151105092448.GC18221@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <87pozpwrao.fsf@Rainer.invalid> <87bnb9wk11.fsf@Rainer.invalid> <877flxwj6z.fsf@Rainer.invalid> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="/e2eDi0V/xtL+Mc8" Content-Disposition: inline In-Reply-To: <877flxwj6z.fsf@Rainer.invalid> User-Agent: Mutt/1.5.23 (2014-03-12) X-SW-Source: 2015-11/txt/msg00109.txt.bz2 --/e2eDi0V/xtL+Mc8 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-length: 1291 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 test > > 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. 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. 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... I applied yet another patch and uploaded a new developer snapshot (this time *with* the ACL changes) to https://cygwin.com/snapshots/ Can you please give it a try ASAP? Thank you, Corinna --=20 Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat --/e2eDi0V/xtL+Mc8 Content-Type: application/pgp-signature Content-length: 819 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWOyBgAAoJEPU2Bp2uRE+gv6cP/RUlO/AjcAMP0RDlG7JfiPpe V5zZLiOz5AOzDkMa1/71s1wDXSy3g8r9vBQE9BF6nW5tEbmsw/FFK3BA5wnR7WnR QHjOqd91PVazirgniAKAWLOAYtlAsns9XUgtv8L7KmnBixEQZBEBwf0arcDEmHWi BBhH7U6q+n7LHFPbbZrUZECZpzGO7T70qakdW4D5SRIiSEEahLbiEjuqspYx7o4x MZx/AIoV6/jKkrh31g45wCXL0CC/9ehOoIJf3FNvvB/r4Hwj6hptGW5DLe9xfRxc c/AvkmZsDiXdYZbLqEp9xLxRrZLWXlQKzVqoV2dTT3qaCMtnrsgBzLa6LqpLa5DB E0fFU13EDdbTIexCoo6czD9M1YhQMGUDgN3ugP5T9xlJaaJgSC7jZBImYNuEfc4J FTemqR1YD8GEKaGUI9Syj9s8m0+v1w80uxV8m38hqIpe3NXXRhe0EvUU2Ra2sPli Jt/Td8xq5RTxB8omNaE4+LKPKZ4AMJZSPjuTG8vIENHj+SdMUXt3aIAyCkd3nf67 o5baAmZJ35keQhuGmJcOrTVr9HMZsrRARyBS9GrMJ/xvRWDha5bTjNMPHqsus3Pk 6Ju+qWEZf0tHUUfLN3vLqxXqVAOdm5A/5W9CPf0MRGpRouByubVZTLxHG1PdPlcm YKQh/i+ZEwva0+ik8rJk =LoL9 -----END PGP SIGNATURE----- --/e2eDi0V/xtL+Mc8--