public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Bob Rossi <bob@brasko.net>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb@sources.redhat.com
Subject: Re: show inferior-tty
Date: Mon, 11 Jul 2005 03:32:00 -0000	[thread overview]
Message-ID: <20050711033228.GB27734@white> (raw)
In-Reply-To: <17105.54757.46681.109597@farnswood.snap.net.nz>

On Mon, Jul 11, 2005 at 02:13:57PM +1200, Nick Roberts wrote:
> 
> Firstly a doc error (GDB/MI -inferior-tty-show):
> 
>    The corresponding GDB command is `show inferior-tty /dev/pts/1'.
> 
> should presumably read:
> 
>    The corresponding GDB command is `show inferior-tty'.

OK, this looks like a good change. I'll also make this.

> Secondly, if I don't set the tty, I get:
> 
> (gdb) show inferior-tty
> Terminal for future runs of program being debugged is "".
> 
> I think that it should still display a value.  Also perhaps it could just
> say e.g
> 
> Terminal for future runs is "/dev/pts/1".

Well, I think this is just preference. GDB has worked like this for
years. I don't mind it the way it is, but if others want it changed,
that's fine too.

> With MI, if I don't set the tty, I get:
> 
> (gdb) 
> -inferior-tty-show
> ^done
> (gdb) 
> 
> Even if its still considered inappropriate to give a value in this case, I
> think it should give a value e.g.
> 
> (gdb) 
> -inferior-tty-show
> ^done,inferior_tty_terminal=""
> (gdb) 

This sounds reasonable.

> Incidentally, I don't see the need for this MI command or -inferior-tty-set
> because:
> 
> (gdb) 
> -gdb-set inferior-tty /dev/pts/1       
> ^done
> (gdb) 
> -gdb-show inferior-tty 
> ^done,value="/dev/pts/1"
> (gdb) 

I was told that it would be a good idea not to bring/use the set/show
variables in GDB/MI. Although, I could have misunderstood the advice 
given to me.

Bob Rossi

  reply	other threads:[~2005-07-11  3:32 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 [this message]
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

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=20050711033228.GB27734@white \
    --to=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).