public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: extra debug output in thread.c Date: Mon, 10 Oct 2022 11:19:25 +0000 (GMT) [thread overview] Message-ID: <20221010111925.B118C3840C09@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=58fd1204aa0f66dd2df30f673c9441e0265b8515 commit 58fd1204aa0f66dd2df30f673c9441e0265b8515 Author: Andrew Burgess <aburgess@redhat.com> Date: Mon Sep 5 16:56:35 2022 +0100 gdb: extra debug output in thread.c Add some extra 'threads' debug in a couple of places in thread.c. I've also added an additional gdb_assert in one case. Diff: --- gdb/thread.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/gdb/thread.c b/gdb/thread.c index 378c5ee2d13..349fc01dd48 100644 --- a/gdb/thread.c +++ b/gdb/thread.c @@ -834,6 +834,10 @@ set_running_thread (struct thread_info *tp, bool running) started = true; tp->state = running ? THREAD_RUNNING : THREAD_STOPPED; + threads_debug_printf ("thread: %s, running? %d%s", + tp->ptid.to_string ().c_str (), running, + (started ? " (started" : "")); + if (!running) { /* If the thread is now marked stopped, remove it from @@ -1298,6 +1302,9 @@ info_threads_command_completer (struct cmd_list_element *ignore, void switch_to_thread_no_regs (struct thread_info *thread) { + gdb_assert (thread != nullptr); + threads_debug_printf ("thread = %s", thread->ptid.to_string ().c_str ()); + struct inferior *inf = thread->inf; set_current_program_space (inf->pspace); @@ -1315,6 +1322,8 @@ switch_to_no_thread () if (current_thread_ == nullptr) return; + threads_debug_printf ("thread = NONE"); + current_thread_ = nullptr; inferior_ptid = null_ptid; reinit_frame_cache ();
reply other threads:[~2022-10-10 11:19 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=20221010111925.B118C3840C09@sourceware.org \ --to=aburgess@sourceware.org \ --cc=gdb-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).