From 4351271e9c98553900f6ae3cbcaaa75198909daa Mon Sep 17 00:00:00 2001 From: Andrew Burgess Date: Fri, 4 Jun 2021 14:31:33 +0100 Subject: [PATCH 1/1] gdb: add some additional debug output in remote.c I needed more debug output from: remote_target::select_thread_for_ambiguous_stop_reply I thought this would be useful for others too. gdb/ChangeLog: * remote.c (remote_target) : Add additional debug output. --- gdb/ChangeLog | 6 ++++++ gdb/remote.c | 8 ++++++++ 2 files changed, 14 insertions(+) diff --git a/gdb/ChangeLog b/gdb/ChangeLog index 875d8b7db0e..99e935ab54f 100644 --- a/gdb/ChangeLog +++ b/gdb/ChangeLog @@ -1,3 +1,9 @@ +2021-06-04 Andrew Burgess + + * remote.c (remote_target) + : Add additional debug + output. + 2021-06-04 Hannes Domani * python/py-tui.c (class tui_py_window): Add click function. diff --git a/gdb/remote.c b/gdb/remote.c index 9b465d77343..de04aab43dc 100644 --- a/gdb/remote.c +++ b/gdb/remote.c @@ -7934,12 +7934,16 @@ ptid_t remote_target::select_thread_for_ambiguous_stop_reply (const struct target_waitstatus *status) { + REMOTE_SCOPED_DEBUG_ENTER_EXIT; + /* Some stop events apply to all threads in an inferior, while others only apply to a single thread. */ bool process_wide_stop = (status->kind == TARGET_WAITKIND_EXITED || status->kind == TARGET_WAITKIND_SIGNALLED); + remote_debug_printf ("process_wide_stop = %d", process_wide_stop); + thread_info *first_resumed_thread = nullptr; bool ambiguous = false; @@ -7959,6 +7963,10 @@ remote_target::select_thread_for_ambiguous_stop_reply ambiguous = true; } + remote_debug_printf ("first resumed thread is %s", + pid_to_str (first_resumed_thread->ptid).c_str ()); + remote_debug_printf ("is this guess ambiguous? = %d", ambiguous); + gdb_assert (first_resumed_thread != nullptr); /* Warn if the remote target is sending ambiguous stop replies. */ -- 2.39.2