public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Don't include buildsym-legacy.h in windows-nat.c
Date: Tue, 15 Oct 2019 01:29:00 -0000 [thread overview]
Message-ID: <dde996e213c916e9440045231a4ac7fda130a888@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT dde996e213c916e9440045231a4ac7fda130a888 ***
commit dde996e213c916e9440045231a4ac7fda130a888
Author: Tom Tromey <tromey@adacore.com>
AuthorDate: Wed Oct 2 13:24:15 2019 -0600
Commit: Tom Tromey <tromey@adacore.com>
CommitDate: Tue Oct 8 11:17:21 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 --git a/gdb/ChangeLog b/gdb/ChangeLog
index c4c7d5f0f0..9b09048cf1 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+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.
diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c
index 26030e0a92..d73e68a4a6 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"
next reply other threads:[~2019-10-15 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 1:29 gdb-buildbot [this message]
2019-10-15 1:29 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot
2019-10-15 3:01 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot
2019-10-15 3:52 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot
2019-10-20 23:16 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2019-10-21 0:23 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot
2019-10-21 0:57 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2019-10-21 1:08 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2019-10-21 1:46 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot
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=dde996e213c916e9440045231a4ac7fda130a888@gdb-build \
--to=gdb-buildbot@sergiodj.net \
--cc=gdb-testers@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).