public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] Remove struct keyword from section_addr_info
Date: Mon, 26 Mar 2018 17:54:00 -0000 [thread overview]
Message-ID: <4f7ae6f5059924a5acc4490880449d6410dc5c93@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 4f7ae6f5059924a5acc4490880449d6410dc5c93 ***
Author: Keith Seitz <keiths@redhat.com>
Branch: master
Commit: 4f7ae6f5059924a5acc4490880449d6410dc5c93
Remove struct keyword from section_addr_info
Buildbot pointed out a failiure in windows-nat.c:
../../binutils-gdb/gdb/windows-nat.c:582:10: error: using typedef-name 'section_addr_info' after 'struct'
struct section_addr_info *addrs;
^~~~~~~~~~~~~~~~~
In file included from ../../binutils-gdb/gdb/windows-nat.c:49:0:
../../binutils-gdb/gdb/symfile.h:75:37: note: 'section_addr_info' has a previous declaration here
typedef std::vector<other_sections> section_addr_info;
^~~~~~~~~~~~~~~~~
A recursive grep of the sources for "struct section_addr_info" reveals one
additional reference in a comment. In both cases, this patch simply removes
the struct keyword.
gdb/ChangeLog:
* symfile.c (place_section): Remove "struct" from section_addr_info
in comment.
* windows-nat.c (struct safe_symbol_file_add_args) <addrs>: Remove
"struct" keyword from section_addr_info.
next reply other threads:[~2018-03-26 17:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 17:54 sergiodj+buildbot [this message]
2018-03-26 17:54 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot
2018-03-26 17:55 ` Failures on Debian-s390x-m64, " sergiodj+buildbot
2018-03-26 17:55 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-03-26 17:58 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2018-03-26 18:02 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-03-26 18:22 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot
2018-03-26 18:37 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-26 18:39 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2018-03-26 18:47 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-03-26 19:08 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2018-03-26 19:13 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2018-03-26 19:26 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+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=4f7ae6f5059924a5acc4490880449d6410dc5c93@gdb-build \
--to=sergiodj+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).