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] Make cp_remove_params return a gdb::unique_xmalloc_ptr
Date: Mon, 09 Oct 2017 15:34:00 -0000 [thread overview]
Message-ID: <109483d9eec3f0d0c3eaafd5d829435059167c52@gdb-build> (raw)
*** TEST RESULTS FOR COMMIT 109483d9eec3f0d0c3eaafd5d829435059167c52 ***
Author: Pedro Alves <palves@redhat.com>
Branch: master
Commit: 109483d9eec3f0d0c3eaafd5d829435059167c52
Make cp_remove_params return a gdb::unique_xmalloc_ptr
Use the type system instead of callers needing to know how the
returned string's memory is supposed to be managed.
gdb/ChangeLog:
2017-10-09 Pedro Alves <palves@redhat.com>
* cp-support.c (cp_remove_params): Return a gdb::unique_xmalloc_ptr.
Use bool.
(overload_list_add_symbol): Adjust to use gdb::unique_xmalloc_ptr.
* cp-support.h (cp_remove_params): Now returns a
gdb::unique_xmalloc_ptr.
* dwarf2read.c (find_slot_in_mapped_hash): Now returns bool.
Adjust to cp_remove_params returning a gdb::unique_xmalloc_ptr.
* psymtab.c (psymtab_search_name): Adjust to cp_remove_params
returning a gdb::unique_xmalloc_ptr.
(lookup_partial_symbol): Adjust to use gdb::unique_xmalloc_ptr.
* stack.c (find_frame_funname): Adjust to cp_remove_params
returning a gdb::unique_xmalloc_ptr.
next reply other threads:[~2017-10-09 15:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 15:34 sergiodj+buildbot [this message]
2017-10-09 15:34 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot
2017-10-09 16:03 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-10-09 16:11 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot
2017-10-09 16:53 ` Failures on Ubuntu-AArch32-native-gdbserver-m32, " sergiodj+buildbot
2017-10-09 17:19 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot
2017-10-09 20:00 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2017-10-09 20:12 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot
2017-10-09 20:20 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-10-09 20:47 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot
2017-10-09 20:59 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot
2017-10-09 21:00 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2017-11-12 4:50 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot
2017-11-12 11:17 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot
2017-11-12 17:44 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot
2017-11-12 18:05 ` *** COMPILATION FAILED *** Failures on Fedora-ppc64be-cc-with-index, branch master *** BREAKAGE *** sergiodj+buildbot
2017-11-24 18:08 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, branch master sergiodj+buildbot
2017-11-24 19:37 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot
2017-11-25 4:54 ` Failures on Fedora-ppc64le-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=109483d9eec3f0d0c3eaafd5d829435059167c52@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).