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 gdb::unique_xmalloc_ptr<> instead of a deleter that invokes free().
Date: Tue, 09 Jan 2018 23:38:00 -0000	[thread overview]
Message-ID: <262f62f57d987269152412a55c458a03adc6ddd6@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 262f62f57d987269152412a55c458a03adc6ddd6 ***

Author: John Baldwin <jhb@FreeBSD.org>
Branch: master
Commit: 262f62f57d987269152412a55c458a03adc6ddd6

Use gdb::unique_xmalloc_ptr<> instead of a deleter that invokes free().

Since xfree() always wraps free(), it is safe to use the xfree deleter
for buffers allocated by library routines such as kinfo_getvmmap() that
must be released via free().

gdb/ChangeLog:

	* fbsd-nat.c (struct free_deleter): Remove.
	(fbsd_find_memory_regions): Use gdb::unique_xmalloc_ptr<>.


             reply	other threads:[~2018-01-09 23:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-09 23:38 sergiodj+buildbot [this message]
2018-01-09 23:38 ` Failures on Fedora-x86_64-native-gdbserver-m32, branch master sergiodj+buildbot
2018-01-09 23:39 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot
2018-01-09 23:42 ` Failures on Fedora-i686, " sergiodj+buildbot
2018-01-09 23:59 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-10  0:04 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot
2018-01-10  3:42 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot
2018-01-10  5:06 ` 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=262f62f57d987269152412a55c458a03adc6ddd6@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).