From 7eb65fafed7b50511f52664e98e22b20eb697197 Mon Sep 17 00:00:00 2001 From: Pedro Alves Date: Fri, 31 Aug 2018 18:47:12 +0100 Subject: Eliminate target_have_continuable_watchpoint target_have_continuable_watchpoint isn't used anywhere so remove it. The property isn't necessary because checking for "continuable" is the same as checking for "!steppable && !non-steppable". gdb/ChangeLog: 2018-08-31 Pedro Alves * nto-procfs.c (nto_procfs_target::have_continuable_watchpoint): Delete. * s390-linux-nat.c (s390_linux_nat_target::have_continuable_watchpoint): Delete. * target.h (target_ops::have_continuable_watchpoint): Delete. (target_have_continuable_watchpoint): Delete. * x86-nat.h (x86_nat_target::have_continuable_watchpoint): Delete. * target-delegates.c: Regenerate. --- gdb/x86-nat.h | 7 ------- 1 file changed, 7 deletions(-) (limited to 'gdb/x86-nat.h') diff --git a/gdb/x86-nat.h b/gdb/x86-nat.h index cc27fa4..c912a00 100644 --- a/gdb/x86-nat.h +++ b/gdb/x86-nat.h @@ -72,13 +72,6 @@ struct x86_nat_target : public BaseTarget { /* Hook in the x86 hardware watchpoints/breakpoints support. */ - /* After a watchpoint trap, the PC points to the instruction after - the one that caused the trap. Therefore we don't need to step - over it. But we do need to reset the status register to avoid - another trap. */ - bool have_continuable_watchpoint () override - { return true; } - int can_use_hw_breakpoint (enum bptype type, int cnt, int othertype) override { return x86_can_use_hw_breakpoint (type, cnt, othertype); } -- cgit v1.1