X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org A2E703854821
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1619620622;
	bh=4GWT7VPDRJJXVzW3CE+GqTePhELdECesjNEHng2PCzI=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=Bg04ePABtQQKgzy0QjVfEejRrY2YZMypv1RWmUDbmd5Ik9aRunjdalrQAp+c8xrH/
	5uZWfYqAvjnHtyNAQthhjjsIsxfCP0OzdEAQPqSBdL6rfb93Stfa8tiqwny0NxOFPr
	B5g6aPkCp1OJkyPidTY9QiqGINze/2lH/mjgu8gg=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 97B19382E82E
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com 13SEaRlM008320
X-Nifty-SrcIP:	[124.155.50.190]
Date:	Wed, 28 Apr 2021 23:36:30 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: 3.2.0-1: possible regression Cygwin DDL bug (W10) when using
	multiple pipes
Message-Id:	<20210428233630.1fd7f4d01d0d452f2f1e7205@nifty.ne.jp>
In-Reply-To:	<499327fb-2b0d-d176-152c-58b195391b01@libero.it>
References:	<499327fb-2b0d-d176-152c-58b195391b01 AT libero DOT it>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-4.1 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_DNSWL_NONE,
	SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<https://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<https://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Wed, 28 Apr 2021 15:38:13 +0200
M2 via Cygwin <cygwin AT cygwin DOT com> wrote:
> Hi,
> I found a possible regression issue between cygwin 3.1.7-1 and 3.2.0-1.
> 
> The issue happens with "short" output in multiple piping, such as the following example:
> 
>     dir | grep c | sed "s/^/foo/" | sed "s/oo/OO/"
> 
> (the case I run is different, but the bug is exposed by something silly/simple as this)
> 
> 
> In 3.1.7, all is fine and you get what you expect.
> 
> In 3.2.0, 3 out of 4 executions hang: the last command on the pipeline (i.e. `sed "s/oo/OO/"`)
> hangs forever, while all preceding commands (i.e. both `grep c` and `sed "s/^/foo/"`) terminate correctly.
> 
> Attached, cygcheck outputs for both 3.1.7 and 3.2.0

I cannot reproduce your problem.

In 64 bit cygwin:

yano AT Express5800-S70 ~
$ uname -a
CYGWIN_NT-10.0 Express5800-S70 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin

yano AT Express5800-S70 ~
$ mkdir abc && cd abc && touch a b c

yano AT Express5800-S70 ~/abc
$ dir | grep c | sed "s/^/foo/" | sed "s/oo/OO/"
fOOa  b  c

yano AT Express5800-S70 ~/abc
$


In 32 bit cygwin:

yano AT Express5800-S70 ~
$ uname -a
CYGWIN_NT-10.0-WOW Express5800-S70 3.2.0(0.340/5/3) 2021-03-29 08:37 i686 Cygwin

yano AT Express5800-S70 ~
$ mkdir abc && cd abc && touch a b c

yano AT Express5800-S70 ~/abc
$ dir | grep c | sed "s/^/foo/" | sed "s/oo/OO/"
fOOa  b  c

yano AT Express5800-S70 ~/abc
$


-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -