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 Alves <pedro@palves.net>
Subject: Re: [PATCH v4 0/4] Make linux checkpoints work with multiple inferiors
Date: Sat, 7 Sep 2024 11:12:54 -0700	[thread overview]
Message-ID: <20240907111254.600b6109@f40-zbm-amd> (raw)
In-Reply-To: <20240626020148.68109-1-kevinb@redhat.com>

Ping.

On Tue, 25 Jun 2024 18:55:51 -0700
Kevin Buettner <kevinb@redhat.com> wrote:

> 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 v2 series incorporates 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 splits out a cosmetic change from the first patch.  It
> capitalizes 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.)
> 
> This v4 series addresses 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.
> 
> 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                           |  23 +-
>  gdb/linux-fork.c                              | 557 +++++++++-----
>  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  | 689 ++++++++++++++++++
>  8 files changed, 1134 insertions(+), 198 deletions(-)
>  create mode 100644 gdb/testsuite/gdb.multi/checkpoint-multi.exp
> 
> -- 
> 2.45.2
> 


  parent reply	other threads:[~2024-09-07 18:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-26  1:55 Kevin Buettner
2024-06-26  1:55 ` [PATCH v4 1/4] " Kevin Buettner
2024-10-23 20:10   ` Pedro Alves
2024-10-31  3:04     ` Kevin Buettner
2024-11-11 18:40       ` Pedro Alves
2024-06-26  1:55 ` [PATCH v4 2/4] Capitalize output of successful checkpoint command Kevin Buettner
2024-06-26  1:55 ` [PATCH v4 3/4] Print only process ptids from linux-fork.c Kevin Buettner
2024-06-26  1:55 ` [PATCH v4 4/4] Linux checkpoints: Update NEWS and gdb.texinfo regarding multiple inferiors Kevin Buettner
2024-06-26 12:25   ` Eli Zaretskii
2024-09-07 18:12 ` Kevin Buettner [this message]
2024-09-30  3:39 ` [PATCH v4 0/4] Make linux checkpoints work with " Kevin Buettner
2024-10-21 18:21 ` 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=20240907111254.600b6109@f40-zbm-amd \
    --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