From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: <gdb-patches@sourceware.org>
Cc: Antoine Tremblay <antoine.tremblay@ericsson.com>
Subject: [PATCH 09/10] Enable software single stepping for while-stepping actions in GDBServer.
Date: Thu, 29 Oct 2015 17:16:00 -0000 [thread overview]
Message-ID: <1446138583-13268-10-git-send-email-antoine.tremblay@ericsson.com> (raw)
In-Reply-To: <1446138583-13268-1-git-send-email-antoine.tremblay@ericsson.com>
This patch enables software single stepping if the targets supports it,
to do while-stepping actions.
No regressions, tested on ubuntu 14.04 ARMv7 and x86.
With gdbserver-{native,extended} / { -marm -mthumb }
gdb/gdbserver/ChangeLog:
* linux-low.c (single_step): New function.
(linux_resume_one_lwp_throw): Call single_step.
(start_step_over): Likewise.
---
gdb/gdbserver/linux-low.c | 59 +++++++++++++++++++++++++++++------------------
1 file changed, 36 insertions(+), 23 deletions(-)
diff --git a/gdb/gdbserver/linux-low.c b/gdb/gdbserver/linux-low.c
index 1f423ba..d0a9c2a 100644
--- a/gdb/gdbserver/linux-low.c
+++ b/gdb/gdbserver/linux-low.c
@@ -3900,7 +3900,34 @@ install_software_single_step_breakpoints (struct lwp_info *lwp)
VEC_free (CORE_ADDR, next_pcs.result);
}
-/* Resume execution of LWP. If STEP is nonzero, single-step it. If
+/* Single step via hardware or software single step.
+ Return 1 if hardware single stepping, 0 if software single stepping
+ or can't single step. */
+
+static int
+single_step (struct lwp_info* lwp)
+{
+ int step = 0;
+
+ if (can_hardware_single_step ())
+ {
+ step = 1;
+ }
+ else if (can_software_single_step ())
+ {
+ install_software_single_step_breakpoints (lwp);
+ step = 0;
+ }
+ else
+ {
+ if (debug_threads)
+ debug_printf ("stepping is not implemented on this target");
+ }
+
+ return step;
+}
+
+/* RESUME execution of LWP. If STEP is nonzero, single-step it. If
SIGNAL is nonzero, give it that signal. */
static void
@@ -4045,14 +4072,13 @@ linux_resume_one_lwp_throw (struct lwp_info *lwp,
address, continue, and carry on catching this while-stepping
action only when that breakpoint is hit. A future
enhancement. */
- if (thread->while_stepping != NULL
- && can_hardware_single_step ())
- {
- if (debug_threads)
- debug_printf ("lwp %ld has a while-stepping action -> forcing step.\n",
- lwpid_of (thread));
- step = 1;
- }
+ if (thread->while_stepping != NULL) {
+ if (debug_threads)
+ debug_printf ("lwp %ld has a while-stepping action -> forcing step.\n",
+ lwpid_of (thread));
+
+ step = single_step (lwp);
+ }
if (proc->tdesc != NULL && the_low_target.get_pc != NULL)
{
@@ -4457,20 +4483,7 @@ start_step_over (struct lwp_info *lwp)
uninsert_breakpoints_at (pc);
uninsert_fast_tracepoint_jumps_at (pc);
- if (can_hardware_single_step ())
- {
- step = 1;
- }
- else if (can_software_single_step ())
- {
- install_software_single_step_breakpoints (lwp);
- step = 0;
- }
- else
- {
- internal_error (__FILE__, __LINE__,
- "stepping is not implemented on this target");
- }
+ step = single_step (lwp);
current_thread = saved_thread;
--
1.9.1
next prev parent reply other threads:[~2015-10-29 17:10 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 17:14 [PATCH 0/10] Support software single step and conditional breakpoints on ARM " Antoine Tremblay
2015-10-29 17:15 ` [PATCH 10/10] Enable conditional breakpoints for targets that support software single step " Antoine Tremblay
2015-11-04 18:58 ` Pedro Alves
2015-10-29 17:15 ` [PATCH 07/10] Share some ARM target dependant code from GDB with GDBServer Antoine Tremblay
2015-11-04 19:56 ` Pedro Alves
2015-11-05 14:44 ` Antoine Tremblay
2015-10-29 17:15 ` [PATCH 04/10] Remove support for thread events without TRACE_EVENT_CLONE in GDBServer Antoine Tremblay
2015-11-03 17:05 ` Yao Qi
2015-11-03 17:24 ` Antoine Tremblay
2015-11-03 17:27 ` [PATCH v2] " Antoine Tremblay
2015-11-04 18:19 ` [PATCH 04/10] " Pedro Alves
2015-11-05 11:43 ` Antoine Tremblay
2015-10-29 17:16 ` Antoine Tremblay [this message]
2015-11-04 18:55 ` [PATCH 09/10] Enable software single stepping for while-stepping actions " Pedro Alves
2015-10-29 17:28 ` [PATCH 03/10] Refactor queries for hardware and software single stepping support " Antoine Tremblay
2015-11-04 18:47 ` Pedro Alves
2015-10-29 17:31 ` [PATCH 05/10] Remove too simple breakpoint_reinsert_addr implementations Antoine Tremblay
2015-11-04 18:21 ` Pedro Alves
2015-10-29 17:36 ` [PATCH 01/10] Fix breakpoint size when stepping over a permanent breakpoint in GDBServer Antoine Tremblay
2015-11-03 16:22 ` Yao Qi
2015-11-03 17:05 ` Antoine Tremblay
2015-10-29 17:43 ` [PATCH 08/10] Support software single step on ARM " Antoine Tremblay
2015-11-04 18:46 ` Pedro Alves
2015-10-29 17:45 ` [PATCH 06/10] Replace breakpoint_reinsert_addr by get_next_pcs operation " Antoine Tremblay
2015-11-04 18:48 ` Pedro Alves
2015-11-05 14:35 ` Antoine Tremblay
2015-10-29 17:48 ` [PATCH 02/10] Fix instruction skipping when using software single step " Antoine Tremblay
2015-11-04 18:08 ` 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=1446138583-13268-10-git-send-email-antoine.tremblay@ericsson.com \
--to=antoine.tremblay@ericsson.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