From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from conssluserg-06.nifty.com (conssluserg-06.nifty.com [210.131.2.91]) by sourceware.org (Postfix) with ESMTPS id 97B19382E82E for ; Wed, 28 Apr 2021 14:36:57 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 97B19382E82E Received: from Express5800-S70 (v050190.dynamic.ppp.asahi-net.or.jp [124.155.50.190]) (authenticated) by conssluserg-06.nifty.com with ESMTP id 13SEaRlM008320; Wed, 28 Apr 2021 23:36:27 +0900 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 From: Takashi Yano To: cygwin@cygwin.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@libero.it> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2021 14:37:01 -0000 On Wed, 28 Apr 2021 15:38:13 +0200 M2 via Cygwin 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@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@Express5800-S70 ~ $ mkdir abc && cd abc && touch a b c yano@Express5800-S70 ~/abc $ dir | grep c | sed "s/^/foo/" | sed "s/oo/OO/" fOOa b c yano@Express5800-S70 ~/abc $ In 32 bit cygwin: yano@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@Express5800-S70 ~ $ mkdir abc && cd abc && touch a b c yano@Express5800-S70 ~/abc $ dir | grep c | sed "s/^/foo/" | sed "s/oo/OO/" fOOa b c yano@Express5800-S70 ~/abc $ -- Takashi Yano