public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Tom Tromey <tromey@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: [PATCH] Remove gdb_stdtargerr
Date: Fri, 17 May 2024 10:07:43 -0600	[thread overview]
Message-ID: <87zfsotoa8.fsf@tromey.com> (raw)
In-Reply-To: <871q60r0qm.fsf@redhat.com> (Andrew Burgess's message of "Fri, 17 May 2024 15:06:57 +0100")

Andrew> I tried to figure out what gdb_stdtarg and gdb_stdtargin are used for,
Andrew> and they both appear to be of pretty limited use.  I wonder what value
Andrew> they are actually adding?

For gdb_stdtargin, I don't know.

For gdb_stdtarg, I think this is one of those MI things that was never
fully implemented.  This stream does use a different prefix:

  mi->out = new mi_console_file (mi->raw_stdout, "~", '"');
  mi->err = new mi_console_file (mi->raw_stdout, "&", '"');
...
  mi->targ = new mi_console_file (mi->raw_stdout, "@", '"');

Based on the code I think the intent here was that target output would
be captured and sent to this MI stream, so the MI user could display it
differently if desired.

However, this was never really implemented, and then even "less
implemented" somehow because output packets were never updated for
non-stop.

This might change again when the "tty" patches land, because IIUC those
will make gdb intercept inferior I/O.

Tom

      reply	other threads:[~2024-05-17 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 13:57 Tom Tromey
2024-05-17 14:06 ` Andrew Burgess
2024-05-17 16:07   ` Tom Tromey [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=87zfsotoa8.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    /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).