From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Cleanup and bug fix related to thread iteration and proceed calls
Date: Thu, 6 Aug 2026 21:53:59 +0100 [thread overview]
Message-ID: <cover.1786049312.git.aburgess@redhat.com> (raw)
After commit:
commit 2e9aaf9455118cee476ea6c4e6aa78477fa84a8e
Date: Wed May 13 09:57:06 2026 -0600
Remove for_each_thread
I spotted a couple of places where we could simplify the code by not
iterating over all_threads, this is patch #1.
And this led me to spot an actual bug in the MI code. Not a bug
introduced by the above commit, this is something that has been in GDB
for a while. This is patch #2.
Thanks,
Andrew
---
Andrew Burgess (2):
gdb: use inferior::threads instead of all_threads and a PID filter
gdb: share some thread proceed related code between CLI and MI
gdb/infcmd.c | 62 ++++++++----
gdb/inferior.h | 11 +++
gdb/mi/mi-main.c | 49 +++-------
gdb/testsuite/gdb.mi/mi-corefile-and-live.c | 37 +++++++
gdb/testsuite/gdb.mi/mi-corefile-and-live.exp | 97 +++++++++++++++++++
5 files changed, 202 insertions(+), 54 deletions(-)
create mode 100644 gdb/testsuite/gdb.mi/mi-corefile-and-live.c
create mode 100644 gdb/testsuite/gdb.mi/mi-corefile-and-live.exp
base-commit: f94273aeb37908c32aa26530ff56e862f0060daf
--
2.25.4
next reply other threads:[~2026-08-06 20:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 20:53 Andrew Burgess [this message]
2026-08-06 20:54 ` [PATCH 1/2] gdb: use inferior::threads instead of all_threads and a PID filter Andrew Burgess
2026-08-07 7:59 ` Tom de Vries
2026-08-06 20:54 ` [PATCH 2/2] gdb: share some thread proceed related code between CLI and MI Andrew Burgess
2026-08-07 9:20 ` Tom de Vries
2026-08-07 15:40 ` Andrew Burgess
2026-08-07 10:14 ` Tom de Vries
2026-08-07 15:31 ` Andrew Burgess
2026-08-07 16:52 ` Tom de Vries
2026-08-24 18:18 ` Andrew Burgess
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=cover.1786049312.git.aburgess@redhat.com \
--to=aburgess@redhat.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