X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E5A2B3858425 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1637623169; bh=ea33libai2i2x7eMhndlh/5kjWxquJwNZFm7Nkawzow=; h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=hoSdidv49xF+7Hun50kZFJdj5fqeKJKmHIbC1qfGyxS6GFt6NlhqJoPTf7tFjwOiq kjRAuKklSYE4KG4oatktp2yfQ+BN7uNm2Gb70NDT00/l4nzEkKDVusLDKGh3cfgrjH t2JuGODyVpADip3G/z6soNqHG1cIkaIetsoEXpuw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7B0673858417 DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-06.nifty.com 1AMNHXBS027916 X-Nifty-SrcIP: [110.4.221.123] Date: Tue, 23 Nov 2021 08:17:41 +0900 To: cygwin AT cygwin DOT com Subject: Re: cygwin 3.3.x: another problem that may be related to pipes Message-Id: <20211123081741.0bf8039de88ceed5b96ad4e7@nifty.ne.jp> In-Reply-To: <1790410068.674967.1637619810958@mail.yahoo.com> References: <115203324 DOT 649908 DOT 1636923059546 DOT ref AT mail DOT yahoo DOT com> <115203324 DOT 649908 DOT 1636923059546 AT mail DOT yahoo DOT com> <20211123002924 DOT a7890a0e1fa58eebd69a6951 AT nifty DOT ne DOT jp> <1790410068 DOT 674967 DOT 1637619810958 AT mail DOT yahoo DOT com> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-4.4 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.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT 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: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Cc: bf Content-Type: text/plain; charset="utf-8" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by delorie.com id 1AMNJVc6024061 On Mon, 22 Nov 2021 22:23:30 +0000 (UTC) bf wrote: > On Tue, 23 Nov 2021 00:29:24 +0900 > Takashi Yano wrote: > > On Sun, 14 Nov 2021 20:50:59 +0000 (UTC) > > bf wrote: > > > I've a shell script that processes several hundred xz-compressed text files with a pipeline of the form: > > > > > > find . -depth -type f  ... -print0 | \ > > > xargs -0tI @ xzcat -- @ | \ > > > iconv --byte-subst='�' --unicode-subst='�' --widechar-subst='�' -f MS-ANSI -t UTF-8 -- | \ > > > grep ... \ > > > sed ... | \ > > > sort ... | \ > > > sort ... > > > > > > . Since updating to cygwin 3.3.x (but not on cygwin 3.2.x) the script consistently fails when decompressing a portion of the files, resulting in lost data, and error messages of the form: > > > > > > xzcat: (stdout): Write error: Bad address > > > > Please try the latest developer snapshot: http://cygwin.com/snapshots/ > > When using the cygwin snapshot of 2021-11-22 13:02:50 UTC, I am unable to reproduce the errors that I saw earlier with cygwin 3.3.x. > > Thank you for your time and effort. Thanks for testing. -- Takashi Yano -- 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