From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/2] gdb: add some additional debug in mark_async_event_handler
Date: Wed, 5 Oct 2022 10:34:39 +0100 [thread overview]
Message-ID: <aac36884bbd08ad07dcebcdffc861cb02599330d.1664962429.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1664962429.git.aburgess@redhat.com>
Extend the existing debug printf call to include the previous state of
the async_event_handler object.
---
gdb/async-event.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gdb/async-event.c b/gdb/async-event.c
index 12ce62cfa5f..8c6ba099f59 100644
--- a/gdb/async-event.c
+++ b/gdb/async-event.c
@@ -293,8 +293,10 @@ create_async_event_handler (async_event_handler_func *proc,
void
mark_async_event_handler (async_event_handler *async_handler_ptr)
{
- event_loop_debug_printf ("marking async event handler `%s`",
- async_handler_ptr->name);
+ event_loop_debug_printf ("marking async event handler `%s` "
+ "(previous state was %d)",
+ async_handler_ptr->name,
+ async_handler_ptr->ready);
async_handler_ptr->ready = 1;
}
--
2.25.4
next prev parent reply other threads:[~2022-10-05 9:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 9:34 [PATCH 0/2] Some additional debug output Andrew Burgess
2022-10-05 9:34 ` Andrew Burgess [this message]
2022-10-05 9:34 ` [PATCH 2/2] gdb: more infrun debug from breakpoint.c Andrew Burgess
2022-10-05 12:27 ` Simon Marchi
2022-10-06 8:45 ` Andrew Burgess
2022-10-06 9:37 ` [PUSHED 0/3] Some additional debug output Andrew Burgess
2022-10-06 9:37 ` [PUSHED 1/3] gdb: add some additional debug in mark_async_event_handler Andrew Burgess
2022-10-06 9:37 ` [PUSHED 2/3] gdb: more infrun debug from breakpoint.c Andrew Burgess
2022-10-06 9:37 ` [PUSHED 3/3] gdb: add missing nullptr checks in bpstat_check_breakpoint_conditions Andrew Burgess
2022-10-06 11:06 ` [PATCH 2/2] gdb: more infrun debug from breakpoint.c Andrew Burgess
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=aac36884bbd08ad07dcebcdffc861cb02599330d.1664962429.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).