Re: MI testsuite improvements

Bob Rossi
2005-02-18T18:00:11Z

On Thu, Feb 17, 2005 at 09:28:45AM -0500, Andrew Cagney 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.

Ok, I'm going to implement this before even thinking about anything
else. Do you care what file the -mi-tty command's go in? or should I
create a new file?

Also, is there an easy way to use the set/show internally to GDB? This
way, as you suggessted, there will be 3 ways to access the inferior's
tty device name.

- through the MI commands
- through the set/show
- and you can only set the tty through the 'tty' console command
there is no way to get the name. This should probably be
depricated ...

Internally, they should all use the same data, so, is there an
interface to modify the set/show value internally to GDB?

Thanks,
Bob Rossi