From: Nick Roberts <nickrob@snap.net.nz>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: show inferior-tty
Date: Tue, 12 Jul 2005 13:34:00 -0000 [thread overview]
Message-ID: <17107.50989.663448.715936@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050712114123.GB1211@white>
> > 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.
Default terminal for future runs of program being debugged is "/dev/pts/1".?
Default terminal for program I/O for future runs is "/dev/pts/1".?
...pitifully trying to salvage something.
Nick
next prev parent reply other threads:[~2005-07-12 13:34 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 [this message]
2005-07-12 14:07 ` Dave Korn
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=17107.50989.663448.715936@farnswood.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=bob@brasko.net \
--cc=gdb@sources.redhat.com \
/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).