Date: Mon, 6 Aug 2001 17:17:23 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Morten Welinder <terra AT diku DOT dk>
cc: djgpp-workers AT delorie DOT com, sandmann AT clio DOT rice DOT edu, pjfarley AT dorsai DOT org,
        snowball3 AT bigfoot DOT com, acottrel AT ihug DOT com DOT au
Subject: Re: Bash 2.05 buffer overrun problem
In-Reply-To: <20010806132236.21723.qmail@tyr.diku.dk>
Message-ID: <Pine.SUN.3.91.1010806171541.26768C-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On 6 Aug 2001, Morten Welinder wrote:

>    Do we have any reason to believe that 32KB is the limit?
> 
> Since you specifically ask "believe", I guess the answer is no.
> But at least the 32KB limit is documented.

It's documented for COMMAND.COM, but not for CMD.EXE, which doesn't even 
have the /e:NNN switch to set the env size, which probably means it 
(gasp!) allocates the environment as necessary.