* [PATCH 0/1] gdb, testsuite: unify 'Switching to thread' message
@ 2026-06-16 13:03 Stephan Rohr
0 siblings, 0 replies; only message in thread
From: Stephan Rohr @ 2026-06-16 13:03 UTC (permalink / raw)
To: gdb-patches
From: "Rohr, Stephan" <stephan.rohr@intel.com>
Hi all,
I observed an inconsistency in the 'Switching to thread' message printed
to the user as implemented in 'normal_stop ()' (in infrun.c) and
'print_selected_thread_frame ()' implemented in thread.c.
I grepped for both versions in the test files, the thread.c version is
more common so I decided to update the message in 'normal_stop ()' to
ensure consistent output.
Let me know if you have any thoughts.
Thanks
Stephan
Rohr, Stephan (1):
gdb, testsuite: unify 'Switching to thread' message
gdb/infrun.c | 3 ++-
gdb/testsuite/gdb.replay/missing-thread.exp | 2 +-
.../gdb.threads/infcall-from-bp-cond-other-thread-event.exp | 2 +-
gdb/testsuite/gdb.threads/infcall-from-bp-cond-timeout.exp | 2 +-
gdb/testsuite/gdb.threads/manythreads.exp | 2 +-
gdb/testsuite/gdb.threads/stepi-over-clone.exp | 5 +++--
6 files changed, 9 insertions(+), 7 deletions(-)
--
2.43.0
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2026-06-16 13:04 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2026-06-16 13:03 [PATCH 0/1] gdb, testsuite: unify 'Switching to thread' message Stephan Rohr
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox