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] Use unique_xmalloc_ptr in two solib functions Date: Mon, 18 Jun 2018 20:13:00 -0000 [thread overview] Message-ID: <309822ca289d602b9f9baf4760329ddd08b1d204@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 309822ca289d602b9f9baf4760329ddd08b1d204 *** Author: Tom Tromey <tom@tromey.com> Branch: master Commit: 309822ca289d602b9f9baf4760329ddd08b1d204 Use unique_xmalloc_ptr in two solib functions This removes a couple of cleanups by using unique_xmalloc_ptr instead. These two changes are combined because the two functions are very similar. gdb/ChangeLog 2018-06-18 Tom Tromey <tom@tromey.com> * solib-frv.c (frv_relocate_main_executable): Use unique_xmalloc_ptr. * solib-dsbt.c (dsbt_relocate_main_executable): Use unique_xmalloc_ptr.
next reply other threads:[~2018-06-18 20:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-06-18 20:13 sergiodj+buildbot [this message] 2018-06-18 20:20 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2018-06-18 23:42 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2018-06-18 23:47 ` Failures on Fedora-i686, " sergiodj+buildbot 2018-06-18 23:58 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2018-06-19 0:16 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2018-06-19 0:18 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2018-06-19 0:25 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2018-06-19 0:35 ` Failures on Fedora-x86_64-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=309822ca289d602b9f9baf4760329ddd08b1d204@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).