From: Pedro Alves <pedro@palves.net>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Use unique_ptr more in the remote target
Date: Fri, 15 Dec 2023 18:12:55 +0000 [thread overview]
Message-ID: <20231215181257.1196830-1-pedro@palves.net> (raw)
A couple cleanup patches improving the ownership tracking in the
remote target.
Pedro Alves (2):
Make cached_reg_t own its data
Complete use of unique_ptr with notif_event and stop_reply
gdb/python/py-unwind.c | 13 +++--
gdb/regcache.h | 5 +-
gdb/remote-notif.c | 15 ++----
gdb/remote-notif.h | 10 ++--
gdb/remote.c | 108 +++++++++++++++++++----------------------
5 files changed, 70 insertions(+), 81 deletions(-)
base-commit: c5a473d789d815c8f03f3ef9fc6df5ccfc40a468
--
2.43.0
next reply other threads:[~2023-12-15 18:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 18:12 Pedro Alves [this message]
2023-12-15 18:12 ` [PATCH 1/2] Make cached_reg_t own its data Pedro Alves
2023-12-20 23:48 ` Simon Marchi
2023-12-21 11:11 ` Pedro Alves
2023-12-15 18:12 ` [PATCH 2/2] Complete use of unique_ptr with notif_event and stop_reply Pedro Alves
2023-12-15 19:10 ` [PATCH 0/2] Use unique_ptr more in the remote target Tom Tromey
2023-12-20 20:27 ` [pushed] Fix bug in previous remote unique_ptr change (Re: [PATCH 0/2] Use unique_ptr more in the remote target) Pedro Alves
2023-12-20 23:30 ` Tom Tromey
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=20231215181257.1196830-1-pedro@palves.net \
--to=pedro@palves.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).