Date:	Wed, 24 Mar 1999 20:35:26 -0500
Message-Id:	<199903250135.UAA01794@mescaline.gnu.org>
From:	Eli Zaretskii <eliz AT gnu DOT org>
To:	djgpp-workers AT delorie DOT com
In-reply-to:	<199903242124.QAA27930@delorie.com> (message from Robert Hoehne
	on Wed, 24 Mar 1999 22:27:49 +0100)
Subject:	Re: Debugging support in DJGPP
References:	<199903231227 DOT HAA22322 AT mescaline DOT gnu DOT org> <199903242124 DOT QAA27930 AT delorie DOT com>
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

   From: Robert Hoehne <robert DOT hoehne AT gmx DOT net>

   This is (at least for me) a well know bug. It manifests itself, if you look
   in the corresponding sources for fsdb, edebug or gdb, where v2loadimage()
   is called, since there the commandline is passed as an array, where the
   [0]th character holds the length of the commandline which can represent
   of course only up to 255 characters. This can be solved using the !proxy
   methode, but I (and probably also others) hadn't the time and motivation
   to do the job [...]

Note that the (not-so-easy) solution to this problem already exists--in
go32-v2.c, it was done for v2.01.  At the time I did that, I didn't
realize that the same problem exists in the debugger support, so the
solution is external to v2loadimage.  But it should be a trivial
matter to copy it to v2loadimage and have it work for the debuggers as
well.  Any volunteers?

(If you want to  know why this is a non-trivial problem, look at the
comments inside go32-v2.c.)

- Raw text -