Re: MI testsuite to use PTY for inferior

Daniel Jacobowitz
2005-07-31T15:31:02Z

On Sun, Jul 31, 2005 at 09:16:53AM -0400, Bob Rossi wrote:
> On Sat, Jul 30, 2005 at 09:21:11PM -0400, Daniel Jacobowitz wrote:
> > On Sat, Jul 30, 2005 at 07:03:09PM -0400, Bob Rossi wrote:
> > > However, since that's pretty ugly, I'll take your suggestion and always
> > > create and assign inferior_pty a value. Then I'll check it for the value
> > > of "true" before executing any code.
> >
> > I recommend doing something different. Make the argument a flag, i.e.
> > "mi_gdb_start use-tty". Or "no-tty" depending on what you want the
> > default to be.
>
> If it would be OK, I'd prefer to just have the TTY work with all MI
> tests, not making it optional. I'd like to repost the patch with all of
> the problems found already, and with that additional change. Is this OK?
>
> My theory is that no FE can/should use MI with out separating the inferior
> output via a pty. So, it's OK to test GDB under these assumptions.

Well, first, let me ask you a question. What is the intended fate of
the old mechanism for interleaved output? The new TTY method has at
least two limitations:

- As far as I know, native Win32 targets can't use PTYs:
http://world.std.com/~jmhart/critcom.htm#UNIX%20Pseudoterminal
So, they'll probably need something different.

- Remote targets that provide output currently aren't redirected onto
the PTY; instead they'll appear interleaved, just like before.

Also, Andrew pretty specifically asked you to leave the mi2-* tests
alone for this change.

--
Daniel Jacobowitz
CodeSourcery, LLC