Date: Sat, 04 Aug 2001 14:39:41 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: acottrel AT ihug DOT com DOT au
Message-Id: <9003-Sat04Aug2001143940+0300-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC: snowball3 AT bigfoot DOT com, djgpp-workers AT delorie DOT com, sandmann AT clio DOT rice DOT edu
In-reply-to: <00cb01c11ccc$ef2fadf0$0a02a8c0@acceleron> (acottrel@ihug.com.au)
Subject: Re: Bash 2.05 buffer overrun problem
References:  <00cb01c11ccc$ef2fadf0$0a02a8c0 AT acceleron>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
> Date: Sat, 4 Aug 2001 20:05:03 +1000
> 
> The quick workarround I have done in the source that I am using is to add
> another buffer after the path_buffer.
>     static char path_buffer[256];
>     static char overrun_buffer[4096]; /* path_buffer is to small */
>     static char *init_cwd;

I think 256 characters is not enough even on Windows 9X: IIRC, the
limitation on environment variables on Windows 9X is 1024 characters.

Bash should probably use alloca instead of a static arbitrary limit.