Date: Wed, 24 Mar 1999 01:49:52 -0500
Message-Id: <199903240649.BAA10763@mescaline.gnu.org>
From: Eli Zaretskii <eliz AT gnu DOT org>
To: pavenis AT lanet DOT lv
CC: djgpp-workers AT delorie DOT com
In-reply-to: <B0000080709@stargate.astr.lu.lv> (pavenis@lanet.lv)
Subject: Re: Debugging support in DJGPP
References: <B0000080657 AT stargate DOT astr DOT lu DOT lv> (pavenis AT lanet DOT lv) <B0000080709 AT stargate DOT astr DOT lu DOT lv>
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

   From: "Andris Pavenis" <pavenis AT lanet DOT lv>

   So I don't see serious problems that would prevent us from using it.

If you think this will be safe, I don't have any objections.  It would
be nice, though, if somebody would build GDB 4.16 with the modified
dbgcom.c and make sure it works.


   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.  It doesn't seem as something really
complicated.  Even if it cannot be solved easily, it would be nice to
know why does that happen.