Re: Bash 2.05 'unsigned char' cleanup

[Brian J. Fox]

   Date: Mon, 7 May 2001 13:03:15 -0700 (PDT)
   From: Paul Eggert <eggert@twinsun.com>

   Description:
           By manual inspection, I found several places where Bash uses
           'unsigned char' where it's cleaner to use 'char' instead.

Interesting evaluation.

           While fixing this, I found one related bug: Bash overruns an
           input buffer while reading the first few bytes of a file to
           see whether it is an executable file.  For example, if the
           file begins with '#', then '!', then 78 spaces, Bash will read
           those 80 bytes into a buffer and then will read past the end
           of the buffer.


I don't see the overrun code.  Perhaps you could explain it to me?

brian