Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: pedro@palves.net, Kevin Buettner <kevinb@redhat.com>
Subject: [PATCH v5 0/4] Make linux checkpoints work with multiple inferiors
Date: Mon,  9 Dec 2024 18:54:03 -0700	[thread overview]
Message-ID: <20241210020313.584564-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 and third patches are largely cosmetic - they
make changes to checkpoint related output.  The fourth patch updates
the documentation.

The v2 series incorporated Pedro's suggestions regarding the
numbering of checkpoint ids.  See the first patch for details.  The
tests have been revised to account for these changes and new tests
have been added as well.

The v3 series split out a cosmetic change from the first patch.  It
capitalized the output of a successful checkpoint command.  This was
prompted by the Linaro regression tester, which, due to the
capitalization change, found two regressions in
gdb.base/kill-during-detach.exp.  (I had made a mistake during my own
testing causing this to not be caught.)

The v4 series addressed Pedro's concerns from his review of the v3
series.  It also adds a NEWS entry and updates the GDB manual with
regard to checkpoint identifiers.

This v5 series makes several changes to the output for the
"info checkpoints" command.  As a consequence, both checkpoint related
tests as well as the documentation were adjusted for these changes.

Kevin Buettner (4):
  Make linux checkpoints work with multiple inferiors
  Capitalize output of successful checkpoint command
  Print only process ptids from linux-fork.c
  Linux checkpoints: Update NEWS and gdb.texinfo regarding multiple
    inferiors

 gdb/NEWS                                      |   2 +
 gdb/doc/gdb.texinfo                           |  20 +-
 gdb/linux-fork.c                              | 590 +++++++++----
 gdb/linux-fork.h                              |  15 +-
 gdb/linux-nat.c                               |  18 +-
 gdb/testsuite/gdb.base/checkpoint.exp         |  26 +-
 gdb/testsuite/gdb.base/kill-during-detach.exp |   2 +-
 gdb/testsuite/gdb.multi/checkpoint-multi.exp  | 800 ++++++++++++++++++
 8 files changed, 1277 insertions(+), 196 deletions(-)
 create mode 100644 gdb/testsuite/gdb.multi/checkpoint-multi.exp

-- 
2.46.2


             reply	other threads:[~2024-12-10  2:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-10  1:54 Kevin Buettner [this message]
2024-12-10  1:54 ` [PATCH v5 1/4] " Kevin Buettner
2025-01-30 17:45   ` Andrew Burgess
2025-02-05 22:06     ` Kevin Buettner
2024-12-10  1:54 ` [PATCH v5 2/4] Capitalize output of successful checkpoint command Kevin Buettner
2024-12-10  1:54 ` [PATCH v5 3/4] Print only process ptids from linux-fork.c Kevin Buettner
2024-12-10  1:54 ` [PATCH v5 4/4] Linux checkpoints: Update NEWS and gdb.texinfo regarding multiple inferiors Kevin Buettner
2024-12-10 13:04   ` Eli Zaretskii
2024-12-19 19:32 ` [PATCH v5 0/4] Make linux checkpoints work with " Tom Tromey
2025-01-30 17:46 ` Andrew Burgess

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=20241210020313.584564-1-kevinb@redhat.com \
    --to=kevinb@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@palves.net \
    /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