Message-Id: <199903242124.QAA27930@delorie.com> From: Robert Hoehne Organization: none provided To: djgpp-workers AT delorie DOT com Date: Wed, 24 Mar 1999 22:27:49 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Debugging support in DJGPP In-reply-to: References: <199903231227 DOT HAA22322 AT mescaline DOT gnu DOT org> X-mailer: Pegasus Mail for Win32 (v3.01d) 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 > As result debugee does not get full command line (it is errorously truncated). It > caused problems for me when I tried to debug cpp.exe and cc1plus.exe. 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 since the task to debug a program with very long commandlines is not so often and in that case you can use the response file (@file) to pass the commandline which will work. > It doesn't > happen when I'm running rhgdb dumparg.exe .... from bash command line or bat I can't imagine that, because of the above description there is really a limitation which can't be fixed by bash or any other extern program. ****************************************************** * email: Robert Hoehne * * Post: Am Berg 3, D-09573 Dittmannsdorf, Germany * * WWW: http://www.tu-chemnitz.de/~sho/rho * ******************************************************