Message-ID: <B0000080916@stargate.astr.lu.lv>
From: "Andris Pavenis" <pavenis AT lanet DOT lv>
To: Martin Str|mberg <ams AT ludd DOT luth DOT se>, djgpp-workers AT delorie DOT com
Date: Wed, 24 Mar 1999 21:50:45 +0200
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Debugging support in DJGPP
In-reply-to: <199903241739.SAA10528@father.ludd.luth.se>
X-mailer: Pegasus Mail for Win32 (v3.02b14)
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 24 Mar 99, at 18:39, Martin Str|mberg wrote:

> Regarding command lines argument not passed to the debugee, I think it
> has always be so in the case of gdb. I even seem to recollect reading
> something about that in a readme file.
> 
I'm not talking about 127 byte limit of command line length as ' ~proxy' method
of transfering arguments is not used is this situation but about bug that prevents 
use of much shorter command lines. I was able even to crash FSDB this way
(no problems when started directly from bash command line or under 
command.com)

Try to run deguging program with long command line (eg 100 bytes) from 
shell script. 

Andris