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] Remove two unused items from windows-nat.c Date: Tue, 15 Oct 2019 04:49:00 -0000 [thread overview] Message-ID: <3abea05d9b60032391971f7fefd44fb4ab560ddd@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 3abea05d9b60032391971f7fefd44fb4ab560ddd *** commit 3abea05d9b60032391971f7fefd44fb4ab560ddd Author: Tom Tromey <tromey@adacore.com> AuthorDate: Tue Oct 8 11:21:46 2019 -0600 Commit: Tom Tromey <tromey@adacore.com> CommitDate: Tue Oct 8 11:21:46 2019 -0600 Remove two unused items from windows-nat.c windows_thread_info_struct::sf is unused, as is struct safe_symbol_file_add_args in windows-nat.c. This patch removes them both. Tested by grep and rebuilding. gdb/ChangeLog 2019-10-08 Tom Tromey <tromey@adacore.com> * windows-nat.c (struct windows_thread_info_struct) <sf>: Remove. (struct safe_symbol_file_add_args): Remove. diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 9b09048cf1..4f6f37b50d 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,8 @@ +2019-10-08 Tom Tromey <tromey@adacore.com> + + * windows-nat.c (struct windows_thread_info_struct) <sf>: Remove. + (struct safe_symbol_file_add_args): Remove. + 2019-10-08 Tom Tromey <tromey@adacore.com> * windows-nat.c: Don't include buildsym-legacy.h. diff --git a/gdb/windows-nat.c b/gdb/windows-nat.c index d73e68a4a6..607b2e8cb9 100644 --- a/gdb/windows-nat.c +++ b/gdb/windows-nat.c @@ -224,7 +224,6 @@ typedef struct windows_thread_info_struct int suspended; int reload_context; CONTEXT context; - STACKFRAME sf; } windows_thread_info; @@ -676,19 +675,6 @@ windows_nat_target::store_registers (struct regcache *regcache, int r) windows_store_one_register (regcache, th, r); } -/* Encapsulate the information required in a call to - symbol_file_add_args. */ -struct safe_symbol_file_add_args -{ - char *name; - int from_tty; - section_addr_info *addrs; - int mainline; - int flags; - struct ui_file *err, *out; - struct objfile *ret; -}; - /* Maintain a linked list of "so" information. */ struct lm_info_windows : public lm_info_base {
next reply other threads:[~2019-10-15 4:49 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-15 4:49 gdb-buildbot [this message] 2019-10-15 4:49 ` Failures on Ubuntu-Aarch64-m64, branch master gdb-buildbot 2019-10-15 6:18 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " gdb-buildbot 2019-10-15 7:07 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, " gdb-buildbot 2019-10-21 1:52 ` Failures on Fedora-i686, " gdb-buildbot 2019-10-21 2:40 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2019-10-21 3:20 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2019-10-21 3:34 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " 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=3abea05d9b60032391971f7fefd44fb4ab560ddd@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: linkBe 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).