Re: MI testsuite improvements

[Bob Rossi <bob at brasko dot net>]

On Thu, Feb 17, 2005 at 11:58:45AM -0500, Alain Magloire wrote:
> > 
> > Bob Rossi wrote:
> > > On Wed, Feb 16, 2005 at 09:41:56AM -0500, Andrew Cagney wrote:
> > > 
> > >>Bob Rossi wrote:
> > >>
> > >>
> > >>>>Let me know what you think. If you want the dbg.log files, I can provide
> > >>>>them.
> > >>
> > >>I was kind of looking for an executive summary :-)  I've attached a 
> > >>trimmed diff.
> > >>
> > >>Two things:
> > >>
> > >>- it should't be using --interpreter console ...
> > >>Can you and/or: add a new -mi-tty command (+test, +doco) and use that; 
> > >>invoke GDB with the --tty=... option.  Your call.  Either pre-approved 
> > >>(but get thumbs up from Eli on the doco).
> > >>
> > >>- can the TTY output be identified in someway?
> > >>That might make debugging easier, but if it isn't possible I guess we 
> > >>live with that.
> > > 
> > > 
> > > OK, I like this idea a lot. I'll make a new mi function that allows you
> > > to set a tty. I'll also make a new MI function that will allow you to
> > > retrieve the tty device being used, both GDB and the inferior.
> > 
> > Ok.  Wonder if it should be ``set/show tty'', "tty ..." just a wrapper.
> > 
> > > Finally, I think it would be helpful to have GDB actually be able to
> > > create a pty for the front end. In case you didn't know, creating a pty
> > > can be a non portable task, and GDB should be capable of doing it every
> > > where it ports to. This would help out the Front Ends a lot. What do you
> > > think? Something like -mi-tty-new -mi-tty-close?
> > 
> > I suspect this is correct.
> > 
> > Alain, how does the CDT currently hande the PTY problem?  Would this be 
> > useful?
> > 
> 
> Yes, it would be.
> The problem comes from local inferior outputs that are intertwine
> with MI stream(The remote case is ok since the output is properly
> wrap in @"..." steam).
> 
> CDT handles this by creating JNI code per platform that
> will create a pseudo pty,  the slave pty is pass to gdb
> 
> 	gdb --tty /dev/ptys/n app
> 
> And the IDE is reading at the other end of the master and
> redirecting the outputs to the IDE console widget.

Yes, this is similar to what I'm doing for CGDB.
> 
> 
> Caveats:
> 
> - Not all platform supports pseudo tty, we still have
>   no solution for Win32/cygwin.

I still did not get GDB on Cygwin to work with the tty command. However,
I did create my own program that opened a pty and spit out the tty
device name and I wrote another program that took that as an argument
and was able to do I/O with the first program. So, I think pty's work
with Cygwin, but for some reason, it doesn't work with GDB on Cygwin.
However, I never looked furthor into it.

At some point, I'll need this to work, so if no one get's there before
me ...

Bob Rossi