From: John Baldwin <jhb@FreeBSD.org>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] Some C++-ification of the FreeBSD target
Date: Tue, 08 Aug 2017 06:20:00 -0000 [thread overview]
Message-ID: <20170808061917.73979-1-jhb@FreeBSD.org> (raw)
Just a few C++ cleanups of the FreeBSD native target. This should remove
the remaining cleanups from the BSD targets other than bsd-uthread.c.
John Baldwin (3):
Fix compile in the !HAVE_KINFO_GETVMMAP case.
Replace remaining cleanups in fbsd-nat.c.
Replace home-grown linked-lists in FreeBSD's native target with
std::list.
gdb/ChangeLog | 26 ++++++++++++
gdb/fbsd-nat.c | 130 ++++++++++++++++++++++-----------------------------------
2 files changed, 75 insertions(+), 81 deletions(-)
--
2.13.3
next reply other threads:[~2017-08-08 6:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-08 6:20 John Baldwin [this message]
2017-08-08 6:20 ` [PATCH 2/3] Replace remaining cleanups in fbsd-nat.c John Baldwin
2017-08-08 9:16 ` Simon Marchi
2017-08-08 15:22 ` John Baldwin
2017-08-08 6:20 ` [PATCH 1/3] Fix compile in the !HAVE_KINFO_GETVMMAP case John Baldwin
2017-08-08 6:20 ` [PATCH 3/3] Replace home-grown linked-lists in FreeBSD's native target with std::list John Baldwin
2017-08-08 9:21 ` Simon Marchi
2017-08-08 15:22 ` John Baldwin
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=20170808061917.73979-1-jhb@FreeBSD.org \
--to=jhb@freebsd.org \
--cc=gdb-patches@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