X-Spam-Check-By: sourceware.org Date: Mon, 23 Jul 2007 17:26:31 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: 1.5.24: data corruption problem with popen and gzip on a text ?mounted filesystem Message-ID: <20070723212631.GB17780@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <46A4BC14 DOT 1050603 AT merl DOT com> <20070723170235 DOT GA17283 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-06) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mon, Jul 23, 2007 at 05:16:26PM +0000, Eric Blake wrote: >Christopher Faylor cygwin.com> writes: >>gzip is linked with binmode.o, like most of the things that I maintain >>(i.e., no upstream patch really necessary - isn't that my call?). If I >>use a really simple test case of just outputting directly to a text >>mode mount, it works fine. > >binmode.o to the contrary, there is indeed a problem: > >$ cd text >$ ls >$ strace -o traceA /bin/ls > /dev/null >$ cp traceA traceB >$ gzip < traceA > traceA.gz >$ gzip < traceB | cat > traceB.gz >$ ls -l >total 88 >-rwxr-xr-x 1 eblake Domain Users 33136 Jul 23 11:12 traceA* >-rw-r--r-- 1 eblake Domain Users 7067 Jul 23 11:12 traceA.gz >-rwxr-xr-x 1 eblake Domain Users 33136 Jul 23 11:12 traceB* >-rw-r--r-- 1 eblake Domain Users 7033 Jul 23 11:12 traceB.gz > >traceA.gz has 34 spurious \r characters. I guess my test case was small enough that this didn't matter. If I made the file bigger I can see the problem. I'll update gzip ASAP. cgf -- 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/