public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/3] gdb: improve infrun_debug_show_threads output
Date: Thu,  6 Oct 2022 18:23:43 +0100	[thread overview]
Message-ID: <c1168e68878f02cc26c7e0b4c9c8e8215d626c10.1665076921.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1665076921.git.aburgess@redhat.com>

This commit switches to use INFRUN_SCOPED_DEBUG_START_END in the
infrun_debug_show_threads function, which means the output will get an
extra level of indentation, this looks a little nicer I think.
---
 gdb/infrun.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/gdb/infrun.h b/gdb/infrun.h
index 0c7c55eabec..226cb3c3e34 100644
--- a/gdb/infrun.h
+++ b/gdb/infrun.h
@@ -62,6 +62,8 @@ infrun_debug_show_threads (const char *title, ThreadRange threads)
 {
   if (debug_infrun)
     {
+      INFRUN_SCOPED_DEBUG_ENTER_EXIT;
+
       infrun_debug_printf ("%s:", title);
       for (thread_info *thread : threads)
 	infrun_debug_printf ("  thread %s, executing = %d, resumed = %d, "
-- 
2.25.4


  reply	other threads:[~2022-10-06 17:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06 17:23 [PATCH 0/3] Another set of debug output patches Andrew Burgess
2022-10-06 17:23 ` Andrew Burgess [this message]
2022-10-06 17:23 ` [PATCH 2/3] gdb: extra debug output in thread.c Andrew Burgess
2022-10-06 17:23 ` [PATCH 3/3] gdb: add infcall specific debugging Andrew Burgess
2022-10-06 17:32   ` Eli Zaretskii
2022-10-10 12:05     ` Andrew Burgess
2022-10-07 19:11 ` [PATCH 0/3] Another set of debug output patches 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=c1168e68878f02cc26c7e0b4c9c8e8215d626c10.1665076921.git.aburgess@redhat.com \
    --to=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).