X-Spam-Check-By: sourceware.org
Message-ID: <454695BC.8E544048@dessent.net>
Date: Mon, 30 Oct 2006 16:15:56 -0800
From: Brian Dessent <brian AT dessent DOT net>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
MIME-Version: 1.0
To: "David L. Morgan" <dmorgan AT aechelon DOT com>
CC: cygwin AT cygwin DOT com
Subject: Re: gzip bug
References: <20061031001840 DOT GA7245 AT ren DOT aechelon DOT com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
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

"David L. Morgan" wrote:

>         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.

You didn't include enough information.  Cygcheck output?  Are you using
text or binary mounts?  What shell do you use?  It wouldn't happen to be
zsh?  Please see this thread from last week:
<http://cygwin.com/ml/cygwin/2006-10/msg00989.html>

Brian

--
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/