This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: MI testsuite improvements
- From: "Alain Magloire" <alain at qnx dot com>
- To: bob at brasko dot net (Bob Rossi)
- Cc: cagney at gnu dot org (Andrew Cagney), alain at qnx dot com (Alain Magloire), nickrob at snap dot net dot nz (Nick Roberts), gdb-patches at sources dot redhat dot com
- Date: Fri, 18 Feb 2005 14:27:24 -0500 (EST)
- Subject: Re: MI testsuite improvements
> >
> > 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?
>
Bob,
I did not see the original of your proposal, so ..
Am I correct to assume that the "show" tty will print the master side
and not the slave or vice versa ...
Meaning the frontends are interested in the other side of the pipe
not the tty given by gdb to the inferior.
--
au revoir, alain