This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Sorry for the incomplete bug report. cygcheck output is attached. I am running BASH, and I tried TCSH to see if you are on the right track, and it behaves the same as BASH. Regards, David On Mon, Oct 30, 2006 at 04:15:56PM -0800, Brian Dessent wrote: > "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 >
Attachment:
cygcheck.txt
Description: Text document
-- 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/
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |