From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/3] gdb: print 'stop_requested' in infrun_debug_show_threads
Date: Thu, 28 Mar 2024 18:35:35 +0100 [thread overview]
Message-ID: <20240328173537.2679010-1-tankut.baris.aktemur@intel.com> (raw)
Print the 'stop_requested' field of a thread in the debug logs.
The field may be useful when debugging GDB's infrun.
---
gdb/infrun.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gdb/infrun.h b/gdb/infrun.h
index 6339fd997e1..57a49da51fe 100644
--- a/gdb/infrun.h
+++ b/gdb/infrun.h
@@ -67,10 +67,11 @@ infrun_debug_show_threads (const char *title, ThreadRange threads)
infrun_debug_printf ("%s:", title);
for (thread_info *thread : threads)
infrun_debug_printf (" thread %s, executing = %d, resumed = %d, "
- "state = %s",
+ "stop_requested = %d, state = %s",
thread->ptid.to_string ().c_str (),
thread->executing (),
thread->resumed (),
+ thread->stop_requested,
thread_state_string (thread->state));
}
}
--
2.34.1
Intel Deutschland GmbH
Registered Address: Am Campeon 10, 85579 Neubiberg, Germany
Tel: +49 89 99 8853-0, www.intel.de <http://www.intel.de>
Managing Directors: Christin Eisenschmid, Sharon Heck, Tiffany Doon Silva
Chairperson of the Supervisory Board: Nicole Lau
Registered Office: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2024-03-28 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 17:35 Tankut Baris Aktemur [this message]
2024-03-28 17:35 ` [PATCH 2/3] gdb: boolify thread_info's 'stop_requested' field Tankut Baris Aktemur
2024-03-28 17:35 ` [PATCH 3/3] gdb: avoid redundant calls to target_stop during attach Tankut Baris Aktemur
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=20240328173537.2679010-1-tankut.baris.aktemur@intel.com \
--to=tankut.baris.aktemur@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