From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 3/6] gdbserver: Add debugging printf when setting last_resume_kind.
Date: Tue, 17 Dec 2013 21:45:00 -0000 [thread overview]
Message-ID: <yjt238lrup75.fsf@ruffy.mtv.corp.google.com> (raw)
Hi.
This patch adds a debugging printf to the setting of last_resume_kind
which I found useful while debugging 16168.
2013-12-17 Doug Evans <dje@google.com>
* linux-low.c (resume_kind_to_str): New function.
(linux_set_resume_request): Add debugging printf when setting
last_resume_kind.
---
gdb/gdbserver/linux-low.c | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
index 464aaf0..3883e50 100644
--- a/gdb/gdbserver/linux-low.c
+++ b/gdb/gdbserver/linux-low.c
@@ -3301,6 +3301,24 @@ struct thread_resume_array
size_t n;
};
+/* Return the string name of KIND. */
+
+static const char *
+resume_kind_to_str (enum resume_kind kind)
+{
+ switch (kind)
+ {
+ case resume_continue:
+ return "resume_continue";
+ case resume_step:
+ return "resume_step";
+ case resume_stop:
+ return "resume_stop";
+ default:
+ gdb_assert_not_reached ("bad resume_kind");
+ }
+}
+
/* This function is called once per thread via find_inferior.
ARG is a pointer to a thread_resume_array struct.
We look up the thread specified by ENTRY in ARG, and mark the thread
@@ -3352,6 +3370,13 @@ linux_set_resume_request (struct inferior_list_entry *entry, void *arg)
lwp->step_range_start = lwp->resume->step_range_start;
lwp->step_range_end = lwp->resume->step_range_end;
+ if (debug_threads)
+ {
+ fprintf (stderr, "setting last_resume_kind of LWP %ld to %s\n",
+ lwpid_of (lwp),
+ resume_kind_to_str (thread->last_resume_kind));
+ }
+
/* If we had a deferred signal to report, dequeue one now.
This can happen if LWP gets more than one signal while
trying to get out of a jump pad. */
--
1.8.5.1
next reply other threads:[~2013-12-17 21:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 21:45 Doug Evans [this message]
2013-12-18 11:16 ` Pedro Alves
2013-12-18 17:31 ` Doug Evans
2013-12-18 17:52 ` Pedro Alves
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=yjt238lrup75.fsf@ruffy.mtv.corp.google.com \
--to=dje@google.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