Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Metzger, Markus T" <markus.t.metzger@intel.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PING] [PATCH v8 0/4] PR gdb/31353
Date: Thu, 30 Apr 2026 11:10:59 +0000	[thread overview]
Message-ID: <DM8PR11MB574940B9A1AD0F8663A09B3ADE352@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20260415072311.3597558-1-markus.t.metzger@intel.com>

Kindly pinging.
Markus.

>-----Original Message-----
>From: Metzger, Markus T <markus.t.metzger@intel.com>
>Sent: Wednesday, April 15, 2026 9:23 AM
>To: gdb-patches@sourceware.org
>Subject: [PATCH v8 0/4] PR gdb/31353
>
>Reviving an old patch series that was first submitted in Jan'21.
>
>It fixes issues with breakpoints at the end of the execution history,
>including PR gdb/31353, which was submitted in the meantime.
>
>Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=31353
>
>Changes in v8:
>  - rebased and resolved conflicts
>
>Changes in v7:
>  - use thread control execution direction in print_no_history_reason()
>
>Changes in v6:
>  - updated tests to use the new end-of-history wording from
>    089197010993b3a5dc50bf882470bab2de696d92
>
>Changes in v5:
>  - remove redundant forward declaration
>
>The changes are mostly in infrun and require global maintainer approval.
>
>Markus Metzger (4):
>  gdb, infrun, btrace: fix reverse/replay stepping at end of execution
>    history
>  gdb, infrun, record: fix hang when step-over fails with no-history
>  gdb, infrun, record: move no-history notification into normal_stop
>  gdb, infrun: fix multi-threaded reverse stepping
>
> gdb/gdbthread.h                               |  13 +++
> gdb/infrun.c                                  | 100 ++++++++++++-----
> gdb/infrun.h                                  |   7 --
> gdb/record-btrace.c                           |  19 ++--
> gdb/testsuite/gdb.btrace/cont-hang.exp        |  43 ++++++++
> .../gdb.btrace/implicit-stop-replaying.exp    | 101 ++++++++++++++++++
> .../gdb.btrace/multi-thread-break-hang.exp    |  85 +++++++++++++++
> gdb/testsuite/gdb.btrace/step-hang.exp        |  42 ++++++++
> gdb/testsuite/gdb.btrace/stepn.exp            |  50 +++++++++
> 9 files changed, 418 insertions(+), 42 deletions(-)
> create mode 100644 gdb/testsuite/gdb.btrace/cont-hang.exp
> create mode 100644 gdb/testsuite/gdb.btrace/implicit-stop-replaying.exp
> create mode 100644 gdb/testsuite/gdb.btrace/multi-thread-break-hang.exp
> create mode 100644 gdb/testsuite/gdb.btrace/step-hang.exp
> create mode 100644 gdb/testsuite/gdb.btrace/stepn.exp
>
>--
>2.34.1

Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928


  parent reply	other threads:[~2026-04-30 11:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-15  7:23 Markus Metzger
2026-04-15  7:23 ` [PATCH v8 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history Markus Metzger
2026-04-15  7:23 ` [PATCH v8 2/4] gdb, infrun, record: fix hang when step-over fails with no-history Markus Metzger
2026-04-15  7:23 ` [PATCH v8 3/4] gdb, infrun, record: move no-history notification into normal_stop Markus Metzger
2026-04-15  7:23 ` [PATCH v8 4/4] gdb, infrun: fix multi-threaded reverse stepping Markus Metzger
2026-04-30 11:10 ` Metzger, Markus T [this message]
2026-07-03  5:43   ` [PING v2] [PATCH v8 0/4] PR gdb/31353 Metzger, Markus T
2026-07-17  8:04     ` [PING v3] " Metzger, Markus T

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=DM8PR11MB574940B9A1AD0F8663A09B3ADE352@DM8PR11MB5749.namprd11.prod.outlook.com \
    --to=markus.t.metzger@intel.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