From 885eeb5b8ea021cc79ffebe8ec40122229c572f0 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Tue, 24 Mar 2015 17:50:30 +0000 Subject: Make step_start_function be per thread I noticed that step_start_function is still a global, while it obviously should be a per-thread field. gdb/ChangeLog: 2015-03-24 Pedro Alves * infrun.c (step_start_function): Delete and ... * gdbthread.h (struct thread_control_state) : ... now a field here. * infrun.c (clear_proceed_status_thread): Clear the thread's step_start_function. (proceed, process_event_stop_test, print_stop_event): Adjust. --- gdb/gdbthread.h | 3 +++ 1 file changed, 3 insertions(+) (limited to 'gdb/gdbthread.h') diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h index e9ae47d..ce4f76f 100644 --- a/gdb/gdbthread.h +++ b/gdb/gdbthread.h @@ -73,6 +73,9 @@ struct thread_control_state CORE_ADDR step_range_start; /* Inclusive */ CORE_ADDR step_range_end; /* Exclusive */ + /* Function the thread was in as of last it started stepping. */ + struct symbol *step_start_function; + /* If GDB issues a target step request, and this is nonzero, the target should single-step this thread once, and then continue single-stepping it without GDB core involvement as long as the -- cgit v1.1