From: Tom Tromey via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Cc: Pedro Alves <pedro@palves.net>
Subject: [PATCH v3 4/6] Remove obsolete comment from gdbthread.h
Date: Thu, 13 Jul 2023 08:05:29 -0600 [thread overview]
Message-ID: <20230713-py-inf-fixes-30615-v3-4-26a024f30553@adacore.com> (raw)
In-Reply-To: <20230713-py-inf-fixes-30615-v3-0-26a024f30553@adacore.com>
A comment in gdbthread.h refers to a global that no longer exists.
Approved-By: Pedro Alves <pedro@palves.net>
---
gdb/gdbthread.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h
index 7135515bf45..d294be6762b 100644
--- a/gdb/gdbthread.h
+++ b/gdb/gdbthread.h
@@ -764,7 +764,7 @@ extern int thread_count (process_stratum_target *proc_target);
/* Return true if we have any thread in any inferior. */
extern bool any_thread_p ();
-/* Switch context to thread THR. Also sets the STOP_PC global. */
+/* Switch context to thread THR. */
extern void switch_to_thread (struct thread_info *thr);
/* Switch context to no thread selected. */
--
2.40.1
next prev parent reply other threads:[~2023-07-13 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 14:05 [PATCH v3 0/6] Fix some Python Inferior methods Tom Tromey via Gdb-patches
2023-07-13 14:05 ` [PATCH v3 1/6] Minor cleanups in py-inferior.exp Tom Tromey via Gdb-patches
2023-07-13 14:05 ` [PATCH v3 2/6] Refactor py-inferior.exp Tom Tromey via Gdb-patches
2023-07-13 14:05 ` [PATCH v3 3/6] Rename Python variable in py-inferior.exp Tom Tromey via Gdb-patches
2023-07-13 14:05 ` Tom Tromey via Gdb-patches [this message]
2023-07-13 14:05 ` [PATCH v3 5/6] Introduce scoped_restore_current_inferior_for_memory Tom Tromey via Gdb-patches
2023-07-13 14:05 ` [PATCH v3 6/6] Use correct inferior in Inferior.read_memory et al Tom Tromey via Gdb-patches
2023-07-14 16:56 ` Pedro Alves
2023-07-14 17:05 ` Tom Tromey
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=20230713-py-inf-fixes-30615-v3-4-26a024f30553@adacore.com \
--to=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=tromey@adacore.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