Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Stephan Rohr <stephan.rohr@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/1] gdb, testsuite: unify 'Switching to thread' message
Date: Tue, 16 Jun 2026 13:03:43 +0000	[thread overview]
Message-ID: <20260616130344.121355-1-stephan.rohr@intel.com> (raw)

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


                 reply	other threads:[~2026-06-16 13:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260616130344.121355-1-stephan.rohr@intel.com \
    --to=stephan.rohr@intel.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