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] Return unique_xmalloc_ptr from some solib.c functions Date: Wed, 14 Feb 2018 15:37:00 -0000 [thread overview] Message-ID: <797bc1cb25b9dbdbc663cf711aecb0acc2450276@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 797bc1cb25b9dbdbc663cf711aecb0acc2450276 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 797bc1cb25b9dbdbc663cf711aecb0acc2450276 Return unique_xmalloc_ptr from some solib.c functions This changes a couple of solib.c functions -- exec_file_find and solib_find -- to return a unique_xmalloc_ptr, and then fixes up the users. This allows the removal of some cleanups. This also changes solib_bfd_open to not take ownership of its argument. I think this change is somewhat cleaner. gdb/ChangeLog 2018-02-14 Tom Tromey <tom@tromey.com> * solist.h (exec_file_find, solib_find): Return unique_xmalloc_ptr. (solib_bfd_fopen): Take a const char *. * solib.c (solib_find_1): Return unique_xmalloc_ptr. (exec_file_find, solib_find): Likewise. (solib_bfd_fopen): Do not take ownership of "pathname". (solib_bfd_open): Use unique_xmalloc_ptr. * solib-darwin.c (darwin_bfd_open): Use unique_xmalloc_ptr. * solib-aix.c (solib_aix_bfd_open): Use unique_xmalloc_ptr. * infrun.c (follow_exec): Use unique_xmalloc_ptr. * exec.c (exec_file_locate_attach): Use unique_xmalloc_ptr.
next reply other threads:[~2018-02-14 15:37 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-14 15:37 sergiodj+buildbot [this message] 2018-02-14 15:37 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-02-14 16:15 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-02-14 16:31 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-02-14 16:39 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-02-14 16:51 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-14 18:18 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-02-14 19:40 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2018-02-15 20:04 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-02-15 20:19 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2018-02-24 9:51 ` Failures on Ubuntu-AArch64-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=797bc1cb25b9dbdbc663cf711aecb0acc2450276@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: 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).