From: Kevin Buettner <kevinb@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
Subject: Re: [PATCH v3] gdb/infrun: do not restart a stepped thread if not running
Date: Sat, 28 Feb 2026 11:33:59 -0700 [thread overview]
Message-ID: <20260228113211.3df714f6@f42-zbm-amd> (raw)
In-Reply-To: <20260223103655.4050848-1-tankut.baris.aktemur@intel.com>
On Mon, 23 Feb 2026 11:36:55 +0100
Tankut Baris Aktemur <tankut.baris.aktemur@intel.com> wrote:
> ======
> Changes in V3:
>
> * Addressed Kevin's comments from
> https://sourceware.org/pipermail/gdb-patches/2026-February/225235.html
>
> * Rebased on the current master; ran regression tests again.
I've looked it over again and have done some testing. LGTM; I think
it's ready to go in.
Approved-by: Kevin Buettner <kevinb@redhat.com>
prev parent reply other threads:[~2026-02-28 18:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 15:24 [PATCH v2] gdb/infrun: do not restart a stepped thread if not running (was: gdb/infrun: reset thread control's step info in end_stepping_range) Tankut Baris Aktemur via Gdb-patches
2023-06-21 12:35 ` Bruno Larsen via Gdb-patches
2023-06-22 7:02 ` Aktemur, Tankut Baris via Gdb-patches
2023-06-22 7:39 ` Bruno Larsen via Gdb-patches
2023-06-22 8:01 ` Aktemur, Tankut Baris via Gdb-patches
2023-11-21 20:00 ` Aktemur, Tankut Baris
2025-02-19 12:52 ` Aktemur, Tankut Baris
2025-03-18 18:11 ` Aktemur, Tankut Baris
2025-04-04 13:44 ` Aktemur, Tankut Baris
2025-04-23 7:59 ` Aktemur, Tankut Baris
2026-02-20 12:11 ` Aktemur, Tankut Baris
2026-02-21 20:44 ` Kevin Buettner
2026-02-23 10:34 ` Aktemur, Tankut Baris
2026-02-23 10:36 ` [PATCH v3] gdb/infrun: do not restart a stepped thread if not running Tankut Baris Aktemur
2026-02-28 18:33 ` Kevin Buettner [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=20260228113211.3df714f6@f42-zbm-amd \
--to=kevinb@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tankut.baris.aktemur@intel.com \
/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