public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] Implement thread_name for gdbserver Date: Thu, 14 Apr 2022 18:21:46 +0000 (GMT) [thread overview] Message-ID: <20220414182146.72EC63858C53@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=42a59714076cc14b1684ce822d3118835d4c6bbe commit 42a59714076cc14b1684ce822d3118835d4c6bbe Author: Tom Tromey <tromey@adacore.com> Date: Tue Apr 12 14:27:13 2022 -0600 Implement thread_name for gdbserver This changes gdbserver to implement thread_name method. Diff: --- gdbserver/win32-low.cc | 9 +++++++++ gdbserver/win32-low.h | 2 ++ 2 files changed, 11 insertions(+) diff --git a/gdbserver/win32-low.cc b/gdbserver/win32-low.cc index 8fde3e95b2d..16c13f32d77 100644 --- a/gdbserver/win32-low.cc +++ b/gdbserver/win32-low.cc @@ -1502,6 +1502,15 @@ win32_process_target::write_pc (struct regcache *regcache, CORE_ADDR pc) return (*the_low_target.set_pc) (regcache, pc); } +const char * +win32_process_target::thread_name (ptid_t thread) +{ + windows_thread_info *th + = windows_process.thread_rec (current_thread_ptid (), + DONT_INVALIDATE_CONTEXT); + return th->name.get (); +} + /* The win32 target ops object. */ static win32_process_target the_win32_target; diff --git a/gdbserver/win32-low.h b/gdbserver/win32-low.h index 8856a84baa3..a1d74573cc9 100644 --- a/gdbserver/win32-low.h +++ b/gdbserver/win32-low.h @@ -158,6 +158,8 @@ public: bool stopped_by_sw_breakpoint () override; bool supports_stopped_by_sw_breakpoint () override; + + const char *thread_name (ptid_t thread) override; }; /* Retrieve the context for this thread, if not already retrieved. */
reply other threads:[~2022-04-14 18:21 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=20220414182146.72EC63858C53@sourceware.org \ --to=tromey@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).