public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] [gdb] Two checkpoint fixes
Date: Mon,  8 Jan 2024 16:25:50 +0100	[thread overview]
Message-ID: <20240108152553.4578-1-tdevries@suse.de> (raw)

While investigating PR31203 "[gdb] FAIL: gdb.base/kill-during-detach.exp: exit_p=true: checkpoint_p=true: python kill_and_detach()" I ran into two checkpoint issues.

I filed these as:
- PR31211 "[gdb] info checkpoints show incorrect info"
- PR31209 "[gdb, delete checkpoint] inferior.c:406: internal-error: find_inferior_pid: Assertion `pid != 0' failed"

This patch series contains fixes for both.

While working on PR31211, I noticed a simplification opportunity in
info_checkpoints_command, so the series starts out with this simplification.

Tested on x86_64-linux.

Tom de Vries (3):
  [gdb] Make variable printed bool in info_checkpoints_command
  [gdb] Fix info checkpoints
  [gdb] Fix assertion failure for checkpoint delete 0

 gdb/linux-fork.c                      | 33 +++++++++++++++++++++++----
 gdb/testsuite/gdb.base/checkpoint.exp | 22 +++++++++++++++---
 2 files changed, 47 insertions(+), 8 deletions(-)


base-commit: 53ba8c111774d318fa572669ba4d3b76121e102b
-- 
2.35.3


             reply	other threads:[~2024-01-08 15:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-08 15:25 Tom de Vries [this message]
2024-01-08 15:25 ` [PATCH 1/3] [gdb] Make variable printed bool in info_checkpoints_command Tom de Vries
2024-01-09 17:54   ` Kevin Buettner
2024-01-08 15:25 ` [PATCH 2/3] [gdb] Fix info checkpoints Tom de Vries
2024-01-09 18:03   ` Kevin Buettner
2024-01-08 15:25 ` [PATCH 3/3] [gdb] Fix assertion failure for checkpoint delete 0 Tom de Vries
2024-01-10  5:28   ` Kevin Buettner
2024-01-10 10:25     ` Tom de Vries

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=20240108152553.4578-1-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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).