From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Kevin Buettner <kevinb@redhat.com>
Subject: [PATCH 0/2] Make linux checkpoints work with multiple inferiors
Date: Sat, 23 Mar 2024 13:27:39 -0700 [thread overview]
Message-ID: <20240323203056.1793487-1-kevinb@redhat.com> (raw)
This series fixes some problems with the current checkpoint code. The
first patch makes the checkpoint code inferior aware, fixing a number
of bugs. The second patch fixes a nit with the way that checkpoints
are sometimes printed.
Kevin Buettner (2):
Make linux checkpoints work with multiple inferiors
Make thread_db_target::pid_to_str checkpoint-aware
gdb/linux-fork.c | 361 ++++++----
gdb/linux-fork.h | 13 +-
gdb/linux-nat.c | 20 +-
gdb/linux-thread-db.c | 4 +-
gdb/testsuite/gdb.multi/checkpoint-multi.exp | 668 +++++++++++++++++++
5 files changed, 925 insertions(+), 141 deletions(-)
create mode 100644 gdb/testsuite/gdb.multi/checkpoint-multi.exp
--
2.44.0
next reply other threads:[~2024-03-23 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 20:27 Kevin Buettner [this message]
2024-03-23 20:27 ` [PATCH 1/2] " Kevin Buettner
2024-03-26 12:55 ` Pedro Alves
2024-03-23 20:27 ` [PATCH 2/2] Make thread_db_target::pid_to_str checkpoint-aware Kevin Buettner
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=20240323203056.1793487-1-kevinb@redhat.com \
--to=kevinb@redhat.com \
--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