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] Don't include buildsym-legacy.h in windows-nat.c
Date: Tue, 08 Oct 2019 17:20:00 -0000	[thread overview]
Message-ID: <20191008172000.60947.qmail@sourceware.org> (raw)

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

commit dde996e213c916e9440045231a4ac7fda130a888
Author: Tom Tromey <tromey@adacore.com>
Date:   Wed Oct 2 13:24:15 2019 -0600

    Don't include buildsym-legacy.h in windows-nat.c
    
    I noticed that windows-nat.c includes buildsym-legacy.h -- but there's
    no reason to do so, as windows-nat.c doesn't create any symbols.
    
    gdb/ChangeLog
    2019-10-08  Tom Tromey  <tromey@adacore.com>
    
    	* windows-nat.c: Don't include buildsym-legacy.h.

Diff:
---
 gdb/ChangeLog     | 4 ++++
 gdb/windows-nat.c | 1 -
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index c4c7d5f..9b09048 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,5 +1,9 @@
 2019-10-08  Tom Tromey  <tromey@adacore.com>
 
+	* windows-nat.c: Don't include buildsym-legacy.h.
+
+2019-10-08  Tom Tromey  <tromey@adacore.com>
+
 	* contrib/ari/gdb_ari.sh (%p): Allow gdb-specific %p extensions.
 
 2019-10-08  Christian Biesinger  <cbiesinger@google.com>
diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index 26030e0..d73e68a 100644
--- a/gdb/windows-nat.c
+++ b/gdb/windows-nat.c
@@ -44,7 +44,6 @@
 #endif
 #include <algorithm>
 
-#include "buildsym-legacy.h"
 #include "filenames.h"
 #include "symfile.h"
 #include "objfiles.h"


                 reply	other threads:[~2019-10-08 17:20 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=20191008172000.60947.qmail@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).