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 cleanups from linux-tdep.c
Date: Sat, 04 Nov 2017 23:25:00 -0000 [thread overview]
Message-ID: <9f584b37e36b67009fa23b6cffbec1bf691ef9ba@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 9f584b37e36b67009fa23b6cffbec1bf691ef9ba ***
Author: Tom Tromey <tom@tromey.com>
Branch: master
Commit: 9f584b37e36b67009fa23b6cffbec1bf691ef9ba
Remove cleanups from linux-tdep.c
This removes some cleanups from linux-tdep.c, replacing them with
def_vector or byte_vector as appropriate.
gdb/ChangeLog
2017-11-04 Tom Tromey <tom@tromey.com>
* linux-tdep.c (linux_core_info_proc_mappings): Use
gdb::def_vector.
(linux_get_siginfo_data): Return gdb::byte_vector. Remove
"size" argument.
(linux_corefile_thread): Update.
(linux_make_corefile_notes): Remove unused variable.
next reply other threads:[~2017-11-04 23:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 23:25 sergiodj+buildbot [this message]
2017-11-04 23:25 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-11-05 2:18 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot
2017-11-05 2:21 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-11-05 2:43 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-11-05 2:55 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-05 3:16 ` Failures on Fedora-i686, " sergiodj+buildbot
2017-11-05 5:35 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-05 5:59 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " 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=9f584b37e36b67009fa23b6cffbec1bf691ef9ba@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).