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:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; q=dns; s=default; b=EFBT/ 7sJGMlKfGGIYsyW/0n/73tvj9BLjZrj4mONsDRLBsixIlnpz9/KyrPmaqKV2vnmu ovM/z1nCuzfJeFzM/fcjwde1rjoScEqJXUcPNuybFcOd0tbeS7d8zS5wu8d0tYX5 2/V+D/QnTXq08ieQ4dLC8k9/DKkNXmm5gtqVz0= 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:from:to:subject:references:date:in-reply-to :message-id:mime-version:content-type; s=default; bh=P9I5rOEOjNc lX0glYAUHhUO7GEs=; b=V62z9OeO1JtLq/VyVC0lGy9Vs1riF/bVu8tCT3l32Jg vrE29+Ts5q3tSv+FgoXO0CwdzMcdS0FmYGamm203AFwo9ud6ul+4TPdrris3WyOV gga6k1XGNY2gV9aE+Jnt1b3LM9WahGsvf+IBYpOJ65chcbcQTZS2O2OsFKOS8w/I = Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-in-05.arcor-online.net X-DKIM: Sendmail DKIM Filter v2.8.2 mail-in-17.arcor-online.net 3nrgyV6Rnkz2hJf From: Achim Gratz To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.6 References: <87pozpwrao DOT fsf AT Rainer DOT invalid> <87bnb9wk11 DOT fsf AT Rainer DOT invalid> Date: Wed, 04 Nov 2015 22:25:40 +0100 In-Reply-To: <87bnb9wk11.fsf@Rainer.invalid> (Achim Gratz's message of "Wed, 04 Nov 2015 22:07:38 +0100") Message-ID: <877flxwj6z.fsf@Rainer.invalid> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain 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. 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. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf Blofeld V1.15B11: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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