Message-ID: From: "Andris Pavenis" To: "Mark E." , djgpp-workers AT delorie DOT com Date: Wed, 24 Mar 1999 22:00:01 +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: <199903241537.PAA22160@out2.ibm.net> References: <199903240649 DOT BAA10763 AT mescaline DOT gnu DOT org> 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 10:37, Mark E. wrote: > > 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. It doesn't happen when I'm running rhgdb dumparg.exe .... > > from bash command line or bat file. I don't know why it happens, but it > > is not a regression against previous versions. It seems to happen only > > when bash is reading input from not from terminal. > > > > If this is a setback relative to prior versions, it would be a good > > idea to try to fix it. > > I tried the example given (after making my own dumpargs.exe) and > found no problems, at least with Bash 2.03. > Well. Downloaded latest binary of bash-2.03 and I saw that the bug is still there. There is no difference between binaries of bash-1.14.7 and bash-2.0.3: the bug appears identically. Andris