From: Christian Franke <Christian.Franke@t-online.de>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: gzip-1.7-1 regression: cannot redirect output of gzip -l
Date: Tue, 19 Apr 2016 11:21:00 -0000 [thread overview]
Message-ID: <1461059351776.571881.3e60150cb042ecb2c8733407f23d3f30c0d10aa5@spica.telekom.de> (raw)
gzip-1.7-1 reports a write error if result of -l is redirected:
$ uname -srvm
CYGWIN_NT-6.1-WOW 2.5.0(0.297/5/3) 2016-04-11 09:55 i686
$ cygcheck -f /bin/gzip
gzip-1.7-1
$ echo text | gzip > text.gz
$ gzip -l text.gz
compressed uncompressed ratio uncompressed_name
25 5 -40.0% text
$ gzip -l text.gz | cat
gzip: write error: Bad file descriptor
$ gzip -l text.gz > out
gzip: write error: Bad file descriptor
This breaks (at least) the zforce script.
gzip -c is not affected.
Christian
--
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
next reply other threads:[~2016-04-19 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 11:21 Christian Franke [this message]
2016-04-19 14:28 ` Eric Blake
2016-04-20 1:34 ` bug#23314: " Paul Eggert
2016-04-20 5:57 ` Paul Eggert
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=1461059351776.571881.3e60150cb042ecb2c8733407f23d3f30c0d10aa5@spica.telekom.de \
--to=christian.franke@t-online.de \
--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).