Date: Thu, 11 Jul 1996 17:47:45 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Oberhumer Markus <k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at>
Cc: djgpp-workers <djgpp-workers AT delorie DOT com>
Subject: Re: gdb crashes if environment too big
In-Reply-To: <199607111355.PAA21159@c210.edvz.uni-linz.ac.at>
Message-Id: <Pine.SUN.3.91.960711174202.7736D-100000@is>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Thu, 11 Jul 1996, Oberhumer Markus wrote:

> Recently I've changed my environment (about 6000 from 8192 bytes used),
> and now I'm encountering a bug when starting gdb or fsdb.

Did you try to stubedit the debugger to a larger transfer buffer and/or 
larger stack size?

> BTW, is someone working with a huge environment > 16 kB ?
> Does this cause troubles with the usual programs (size of the
> transfer buffer) ?

It most probably would make trouble with nested programs.  The transfer 
buffer is used to pass the environment to the child process when spawning 
sub-programs (like gcc does when it invokes the compiler passes).  If 
your environment is approaching 8K, you need to stibedit all the programs 
that can launch other programs to enlarge the transfer buffer.

I think dosexec.c in the library should test for such contingencies and 
print a message (I don't know off hand if it does now).