From: "Dave Korn" <dave.korn@artimi.com>
To: "'Nick Roberts'" <nickrob@snap.net.nz>, "'Bob Rossi'" <bob@brasko.net>
Cc: <gdb@sources.redhat.com>
Subject: RE: show inferior-tty
Date: Tue, 12 Jul 2005 14:07:00 -0000 [thread overview]
Message-ID: <SERRANO4lk9QduLqmD1000004d1@SERRANO.CAM.ARTIMI.COM> (raw)
In-Reply-To: <17107.50989.663448.715936@farnswood.snap.net.nz>
----Original Message----
>From: Nick Roberts
>Sent: 12 July 2005 14:36
> > > What has worked like this for years? "show inferior-tty" is new
> isn't it? >
> > Sorry for the lack of information. The "inferior-tty" is simply a
> better > "tty" command. The tty command has had this documentation,
> > (gdb) help tty
> > Set terminal for future runs of program being debugged.
> >
> > > The phrase "of program being debugged" seems redundant to me (what
> other > > possibilities are there?). It might be even more clear to say:
> > >
> > > Default terminal for future runs is "/dev/pts/1".
> > >
> > > since the redirection overrides this.
> >
> > I like your suggestion. There is still 1 ambiguity though. Is the
> "Default > terminal for future runs" for GDB's I/O? or for the
> inferior's I/O? I think > this question is why the phrase "program being
> debugged" is used.
>
> I guess thats the reason for "of program being debugged" and explains why
> it was a dumb suggestion.
It's not an entirely dumb suggestion. It's a clumsy piece of wording and
could do with being improved.
And since "program being debugged" == "inferior", I'd think the best
choice of wording would be ...
> (gdb) help tty
> Set terminal for future runs of inferior.
cheers,
DaveK
--
Can't think of a witty .sigline today....
prev parent reply other threads:[~2005-07-12 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 2:13 Nick Roberts
2005-07-11 3:32 ` Bob Rossi
2005-07-11 13:10 ` Daniel Jacobowitz
2005-07-11 21:28 ` Nick Roberts
2005-07-12 2:07 ` Nick Roberts
2005-07-12 11:41 ` Bob Rossi
2005-07-12 13:34 ` Nick Roberts
2005-07-12 14:07 ` Dave Korn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SERRANO4lk9QduLqmD1000004d1@SERRANO.CAM.ARTIMI.COM \
--to=dave.korn@artimi.com \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).