From: Markus Metzger <markus.t.metzger@intel.com>
To: gdb-patches@sourceware.org
Cc: pedro@palves.net
Subject: [PATCH v5 0/4] PR gdb/31353
Date: Wed, 10 Apr 2024 07:46:09 +0000 [thread overview]
Message-ID: <20240410074613.54520-1-markus.t.metzger@intel.com> (raw)
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
Guinevere Larsen reviewed most of the series and reported an issue with
applying the last patch. I'm resending the series, rebased on current
master, to hopefully fix that issue.
The only change to v4 is that a redundant forward declaration was removed.
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 | 86 +++++++++++++-----
gdb/infrun.h | 7 --
gdb/record-btrace.c | 19 ++--
gdb/testsuite/gdb.btrace/cont-hang.exp | 43 +++++++++
.../gdb.btrace/implicit-stop-replaying.exp | 90 +++++++++++++++++++
.../gdb.btrace/multi-thread-break-hang.exp | 84 +++++++++++++++++
gdb/testsuite/gdb.btrace/step-hang.exp | 42 +++++++++
gdb/testsuite/gdb.btrace/stepn.exp | 50 +++++++++++
9 files changed, 398 insertions(+), 36 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: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2024-04-10 7:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 7:46 Markus Metzger [this message]
2024-04-10 7:46 ` [PATCH v5 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history Markus Metzger
2024-04-10 7:46 ` [PATCH v5 2/4] gdb, infrun, record: fix hang when step-over fails with no-history Markus Metzger
2024-04-10 7:46 ` [PATCH v5 3/4] gdb, infrun, record: move no-history notification into normal_stop Markus Metzger
2024-04-10 7:46 ` [PATCH v5 4/4] gdb, infrun: fix multi-threaded reverse stepping Markus Metzger
2024-04-12 19:50 ` Guinevere Larsen
2024-04-15 9:03 ` Metzger, Markus T
2024-04-15 12:44 ` Guinevere Larsen
2024-05-03 5:26 ` [PING] [PATCH v5 0/4] PR gdb/31353 Metzger, Markus T
2024-06-07 5:06 ` [PING v2] " Metzger, Markus T
2024-06-27 19:12 ` Guinevere Larsen
2024-09-13 10:43 ` [PING v3] " Metzger, Markus T
2024-10-09 14:10 ` [PING v4] " Metzger, Markus T
2024-10-21 8:45 ` Andrew Burgess
2024-10-21 9:13 ` Andrew Burgess
2024-10-21 9:46 ` 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=20240410074613.54520-1-markus.t.metzger@intel.com \
--to=markus.t.metzger@intel.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