From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/4] Make "checkpoint" not rely on inferior_ptid
Date: Tue, 05 Mar 2019 18:43:00 -0000 [thread overview]
Message-ID: <20190305184340.26768-1-palves@redhat.com> (raw)
Patch #1 is a patch that I had on the multi-target branch. Patches
#2-#4 are follow up C++ifications/cleanups while I was at it.
Pedro Alves (4):
Make "checkpoint" not rely on inferior_ptid
C++ify fork_info, use std::list
linux-fork.c: rewrite inf_has_multiple_threads
Eliminate fork_info::clobber_regs
gdb/linux-fork.c | 377 ++++++++++++++++++++++++-------------------------------
gdb/linux-fork.h | 2 +-
2 files changed, 163 insertions(+), 216 deletions(-)
--
2.14.4
next reply other threads:[~2019-03-05 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 18:43 Pedro Alves [this message]
2019-03-05 18:43 ` [PATCH 1/4] " Pedro Alves
2019-03-05 19:32 ` Tom Tromey
2019-03-05 19:46 ` Pedro Alves
2019-03-05 18:43 ` [PATCH 4/4] Eliminate fork_info::clobber_regs Pedro Alves
2019-03-05 18:43 ` [PATCH 2/4] C++ify fork_info, use std::list Pedro Alves
2019-03-05 18:43 ` [PATCH 3/4] linux-fork.c: rewrite inf_has_multiple_threads Pedro Alves
2019-03-05 19:46 ` [PATCH 0/4] Make "checkpoint" not rely on inferior_ptid 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=20190305184340.26768-1-palves@redhat.com \
--to=palves@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