aboutsummaryrefslogtreecommitdiff
path: root/gdb/gdbserver/linux-low.h
diff options
context:
space:
mode:
authorYao Qi <yao.qi@linaro.org>2016-04-28 11:52:23 +0100
committerYao Qi <yao.qi@linaro.org>2016-04-28 11:52:23 +0100
commitf166f943f30a91792e8754cbca9d7652fc400aae (patch)
tree21d22d77b58abb16daf53ddca47c5ce800fe571f /gdb/gdbserver/linux-low.h
parent4bd13cde17a27c342b79b72bde9ef8e1b5373344 (diff)
downloadgdb-f166f943f30a91792e8754cbca9d7652fc400aae.zip
gdb-f166f943f30a91792e8754cbca9d7652fc400aae.tar.gz
gdb-f166f943f30a91792e8754cbca9d7652fc400aae.tar.bz2
Remove need_step_over from struct lwp_info
Hi, I happen to see that field need_step_over in struct lwp_info is only used to print a debug info. need_step_over is set in linux_wait_1 when breakpoint_here is true, however, we check breakpoint_here too in need_step_over_p and do the step over. I think we don't need field need_step_over, and check breakpoint_here directly in need_step_over_p. This field was added in this patch https://sourceware.org/ml/gdb-patches/2010-03/msg00605.html and the code wasn't changed much since then. This patch is to remove it. gdb/gdbserver: 2016-04-28 Yao Qi <yao.qi@linaro.org> * linux-low.h (struct lwp_info) <need_step_over>: Remove. * linux-low.c (linux_wait_1): Update. (need_step_over_p): Likewise.
Diffstat (limited to 'gdb/gdbserver/linux-low.h')
-rw-r--r--gdb/gdbserver/linux-low.h4
1 files changed, 0 insertions, 4 deletions
diff --git a/gdb/gdbserver/linux-low.h b/gdb/gdbserver/linux-low.h
index d4946c1..6e7ddbd 100644
--- a/gdb/gdbserver/linux-low.h
+++ b/gdb/gdbserver/linux-low.h
@@ -365,10 +365,6 @@ struct lwp_info
a exit-jump-pad-quickly breakpoint. This is it. */
struct breakpoint *exit_jump_pad_bkpt;
- /* True if the LWP was seen stop at an internal breakpoint and needs
- stepping over later when it is resumed. */
- int need_step_over;
-
#ifdef USE_THREAD_DB
int thread_known;
/* The thread handle, used for e.g. TLS access. Only valid if