From: "Metzger, Markus T via Gdb-patches" <gdb-patches@sourceware.org>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "pedro@palves.net" <pedro@palves.net>
Subject: RE: [PATCH v3 0/4] gdb, btrace: infrun fixes
Date: Mon, 29 Aug 2022 04:41:01 +0000 [thread overview]
Message-ID: <DM8PR11MB57498FF4A299036424F61FF0DE769@DM8PR11MB5749.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220704115407.1239498-1-markus.t.metzger@intel.com>
ping,
markus.
>-----Original Message-----
>From: Metzger, Markus T <markus.t.metzger@intel.com>
>Sent: Montag, 4. Juli 2022 13:54
>To: gdb-patches@sourceware.org
>Cc: pedro@palves.net
>Subject: [PATCH v3 0/4] gdb, btrace: infrun fixes
>
>Changes in v3:
> - fix an assertion in clean_up_just_stopped_threads_fsms after
> finish_step_over changed the current thread.
>
>Changes in v2:
> - address feedback from Pedro Alves
>
>There's still an open question raised here:
>https://sourceware.org/pipermail/gdb-patches/2021-November/183700.html.
>
> I'm wondering if prepare_one_step() should reset tp->control.step_stop
> to zero. It does re-initialize tp->control.step_range_start/end and
> we do start another step.
>
>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 | 88 +++++++++++----
> gdb/infrun.h | 7 --
> gdb/record-btrace.c | 19 ++--
> gdb/testsuite/gdb.btrace/cont-hang.exp | 47 ++++++++
> .../gdb.btrace/implicit-stop-replaying.exp | 105 ++++++++++++++++++
> .../gdb.btrace/multi-thread-break-hang.exp | 88 +++++++++++++++
> gdb/testsuite/gdb.btrace/step-hang.exp | 46 ++++++++
> gdb/testsuite/gdb.btrace/stepn.exp | 54 +++++++++
> 9 files changed, 431 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.35.3
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
prev parent reply other threads:[~2022-08-29 4:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 11:54 Markus Metzger via Gdb-patches
2022-07-04 11:54 ` [PATCH v3 1/4] gdb, infrun, btrace: fix reverse/replay stepping at end of execution history Markus Metzger via Gdb-patches
2022-07-04 11:54 ` [PATCH v3 2/4] gdb, infrun, record: fix hang when step-over fails with no-history Markus Metzger via Gdb-patches
2022-07-04 11:54 ` [PATCH v3 3/4] gdb, infrun, record: move no-history notification into normal_stop Markus Metzger via Gdb-patches
2022-07-04 11:54 ` [PATCH v3 4/4] gdb, infrun: fix multi-threaded reverse stepping Markus Metzger via Gdb-patches
2022-08-29 4:41 ` Metzger, Markus T via Gdb-patches [this message]
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=DM8PR11MB57498FF4A299036424F61FF0DE769@DM8PR11MB5749.namprd11.prod.outlook.com \
--to=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
--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