public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Remove two unused members from mi_interp
Date: Wed, 31 Aug 2022 17:14:35 +0000 (GMT)	[thread overview]
Message-ID: <20220831171435.8371F3854156@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=5a09f120568d433872267887ff844b2278b9c09b

commit 5a09f120568d433872267887ff844b2278b9c09b
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Aug 11 10:24:48 2022 -0600

    Remove two unused members from mi_interp
    
    These members of mi_interp aren't used and can be removed.

Diff:
---
 gdb/mi/mi-interp.c | 1 -
 gdb/mi/mi-interp.h | 8 ++------
 2 files changed, 2 insertions(+), 7 deletions(-)

diff --git a/gdb/mi/mi-interp.c b/gdb/mi/mi-interp.c
index ed097cf5d5f..dbf71185ea7 100644
--- a/gdb/mi/mi-interp.c
+++ b/gdb/mi/mi-interp.c
@@ -1297,7 +1297,6 @@ mi_interp::set_logging (ui_file_up logfile, bool logging_redirect,
 	}
 
       mi->raw_stdout = logging_redirect ? logfile_p : tee;
-      mi->raw_stdlog = debug_redirect ? logfile_p : tee;
     }
   else
     {
diff --git a/gdb/mi/mi-interp.h b/gdb/mi/mi-interp.h
index adf6eaffef4..d89439f54c5 100644
--- a/gdb/mi/mi-interp.h
+++ b/gdb/mi/mi-interp.h
@@ -52,14 +52,10 @@ public:
   /* Raw console output.  */
   struct ui_file *raw_stdout;
 
-  /* Raw logfile output.  */
-  struct ui_file *raw_stdlog;
-
-  /* Save the original value of raw_stdout and raw_stdlog here when logging, and
-     the file which we need to delete, so we can restore correctly when
+  /* Save the original value of raw_stdout here when logging, and the
+     file which we need to delete, so we can restore correctly when
      done.  */
   struct ui_file *saved_raw_stdout;
-  struct ui_file *saved_raw_stdlog;
   struct ui_file *saved_raw_file_to_delete;

                 reply	other threads:[~2022-08-31 17:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220831171435.8371F3854156@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@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).