GNU bug report logs - #33878
zcat vs zcat -f -- different output

Previous Next

Full log

Message #13 received at 33878-done <at> debbugs.gnu.org (full text, mbox):

From: Namikaze Minato <lloydsensei <at> gmail.com>
To: 33878-done <at> debbugs.gnu.org
Subject: Re: bug#33878: zcat vs zcat -f -- different output
Date: Thu, 27 Dec 2018 14:09:37 +0100

Thanks a lot for the explanation!
I checked and my files do contain unexpected NUL-byte trailing!

Have a nice day.
Minato

On Wed, 26 Dec 2018 at 19:03, Paul Eggert <eggert <at> cs.ucla.edu> wrote:
>
> Namikaze Minato wrote:
>
> > Do you know what could be happening?
>
> When gzip -cdf sees junk input data, it simply copies it to standard output;
> this behavior is documented in the gzip manual (look for --force). Your input
> files have NUL-byte padding at the end, contrary to Internet RFC 1952.
>
> > Do you know how I could try to reproduce the problem on
> > non-confidential data for you to be able to debug?
>
> $ (gzip </dev/null; printf '\0') >t.gz
> $ gzip -cd <t.gz | od -c
> 0000000
> $ gzip -cdf <t.gz | od -c
> 0000000  \0
> 0000001
>
> Though it's not a bug....

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.