mirror/binutils-gdb
2
0
Fork 0
mirror of https://sourceware.org/git/binutils-gdb.git synced 2024-12-27 04:52:05 +08:00
Code Issues Packages Projects Releases Wiki Activity

gdb/infrun: some extra infrun debug print statements

Browse Source 
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.
This commit is contained in:
Andrew Burgess 2022-02-10 09:59:23 +00:00
parent 577a2a5f20
commit c8353d682f
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
gdb/infrun.c
View File

@ -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);