delorie.com/archives/browse.cgi | search |
X-Spam-Check-By: | sourceware.org |
Date: | Mon, 30 Oct 2006 18:18:40 -0600 |
From: | "David L. Morgan" <dmorgan AT aechelon DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | gzip bug |
Message-ID: | <20061031001840.GA7245@ren.aechelon.com> |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.5.6i |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Hi All, I have uncovered a bug in the version of gzip currently shipping with cygwin (1.3.5-2). I have a binary file that was compressed with gzip 1.3.3 from around 820MB to around 260MB. If I gunzip the file using the default invocation: gunzip file.gz ... everything works fine. If I use the stdout invocation: gunzip -c file.gz > file ... the resulting file differs from the original. Gunzip does not report any errors. A cursory Google search does not yield any relevant bug reports or resolutions. This is on an x86 system running Cygwin 1.5.21-1 Regards, David Morgan dmorgan AT aechelon DOT com -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |