Re: Broken MI output

[Bob Rossi <bob@brasko.net>]

On Thu, Mar 03, 2005 at 05:55:11PM +0300, Karganov Konstantin wrote:
> On Thu, 3 Mar 2005, Bob Rossi wrote:
> 
> > A target program most likely has a special form of I/O, which is
> If gdb was attached to running process - yes, the program has own IO from 
> the starting time and gdb/MI has it's own IO - all is fine here.
> 
> > redirected through GDB. A program running on the host outputs directly
> > to the terminal, and it's impossible for GDB to know anything about it.
> But if the debuggee is started inside gdb it shares the same tty with the 
> debugger.
> The problem of breaking MI grammar with inferior output, can be solved 
> adding a pipe to/from the inferior, monitoring the pipe and quoting target 
> output. 

GDB doesn't currently create pty's for the inferior. So this would be a feature 
request that I've asked about here, 
   http://sources.redhat.com/ml/gdb/2005-03/msg00024.html

> > When GDB is in MI mode, why couldn't it put a pty between the inferior
> > and itself.
> And redirect it to the same terminal, where gdb is started? Or where?
> 
> The only reasonable solution I see here is to have distinct ttys for a 
> inferior (that is controlled by the operator) and for gdb (that is 
> controlled by a GUI using MI).

I don't really know of a project that use's the MI and doesn't give the
inferior it's own tty to work with.

Thanks,
Bob Rossi