From: Andrew Burgess <aburgess@redhat.com>
Date: Thu, 10 Feb 2022 09:59:23 +0000 (+0000)
Subject: gdb/infrun: some extra infrun debug print statements
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=c8353d682f69e2761e1f57040a385a9afdb29655;p=binutils-gdb.git

gdb/infrun: some extra infrun debug print statements

While reviewing a different patch I wanted to know more about what was
going on during GDB's stepping.  I added some extra infrun debug print
calls, and I thought these might be useful to others.
---

diff --git a/gdb/infrun.c b/gdb/infrun.c
index 61af16238de..a3438d1e5c2 100644
--- a/gdb/infrun.c
+++ b/gdb/infrun.c
@@ -4186,6 +4186,12 @@ set_step_info (thread_info *tp, struct frame_info *frame,
 
   tp->current_symtab = sal.symtab;
   tp->current_line = sal.line;
+
+  infrun_debug_printf
+    ("symtab = %s, line = %d, step_frame_id = %s, step_stack_frame_id = %s",
+     tp->current_symtab->filename, tp->current_line,
+     tp->control.step_frame_id.to_string ().c_str (),
+     tp->control.step_stack_frame_id.to_string ().c_str ());
 }
 
 /* Clear context switchable stepping state.  */
@@ -7260,6 +7266,11 @@ process_event_stop_test (struct execution_control_state *ecs)
   ecs->event_thread->control.step_range_start = stop_pc_sal.pc;
   ecs->event_thread->control.step_range_end = stop_pc_sal.end;
   ecs->event_thread->control.may_range_step = 1;
+  infrun_debug_printf
+    ("updated step range, start = %s, end = %s, may_range_step = %d",
+     paddress (gdbarch, ecs->event_thread->control.step_range_start),
+     paddress (gdbarch, ecs->event_thread->control.step_range_end),
+     ecs->event_thread->control.may_range_step);
   if (refresh_step_info)
     set_step_info (ecs->event_thread, frame, stop_pc_sal);