From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Cc: bf <bf2006a@yahoo.com>
Subject: Re: cygwin 3.3.x: another problem that may be related to pipes
Date: Tue, 23 Nov 2021 08:17:41 +0900 [thread overview]
Message-ID: <20211123081741.0bf8039de88ceed5b96ad4e7@nifty.ne.jp> (raw)
In-Reply-To: <1790410068.674967.1637619810958@mail.yahoo.com>
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 <takashi.yano@nifty.ne.jp>
prev parent reply other threads:[~2021-11-22 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <115203324.649908.1636923059546.ref@mail.yahoo.com>
2021-11-14 20:50 ` bf
2021-11-15 8:18 ` Takashi Yano
[not found] ` <20211123002924.a7890a0e1fa58eebd69a6951@nifty.ne.jp>
[not found] ` <1790410068.674967.1637619810958@mail.yahoo.com>
2021-11-22 23:17 ` Takashi Yano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211123081741.0bf8039de88ceed5b96ad4e7@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=bf2006a@yahoo.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).