bug#49721: closed (NAME flag incorrectly set)

[GNU bug Tracking System]

Your message dated Sun, 25 Jul 2021 08:29:32 -0700
with message-id <db2cce4e-4fd3-a124-83d5-d5fa3b93c09a@cs.ucla.edu>
and subject line Re: bug#49721: NAME flag incorrectly set
has caused the debbugs.gnu.org bug report #49721,
regarding NAME flag incorrectly set
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
49721: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=49721
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> NAME flag incorrectly set
>
>
>
>
> Date: 
>
> Sat, 24 Jul 2021 11:14:25 +0100
>
>
>
>
> I've been following a guide on the deflate algorithm (because I wanted
> one where I could control how memory is allocated just as Lua allows)
> and found when I put this:
>
> echo "hello hello hello hello" | gzip
>
> into the terminal gzip incorrectly set the NAME flag, it was only
> after editing it out I was able to deflate the resulting file, the
> same applies for this:
>
> echo -n "abaabbbabaababbaababaaaabaaabbbbbaa" | gzip
>
> Both of which are the examples given on
> https://blog.za3k.com/understanding-gzip-2/
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#49721: NAME flag incorrectly set
>
>
>
>
> Date: 
>
> Sun, 25 Jul 2021 08:29:32 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
>
>
>
>
> On 7/25/21 8:24 AM, Lee Shallis wrote:
> > I just noticed my misunderstanding, seems because I forgot to read the
> > compression byte as a compression byte, it got read as the flags byte,
> > so I was off by a byte when reading the flags without realising.
>
> Thanks for following up. Closing the bug report.
>
>
> --- End Message ---