summaryrefslogtreecommitdiff
path: root/gdb/config/i386
diff options
context:
space:
mode:
authorKris Warkentin <kewarken@qnx.com>2003-02-24 21:56:51 +0000
committerKris Warkentin <kewarken@qnx.com>2003-02-24 21:56:51 +0000
commited64e7e055ec09c7f30f00996407db8c414f6468 (patch)
treece7c340ab26e408b1feb03e7d1bfbb79d15e60bd /gdb/config/i386
parent439ff555d05bdc441f940c3f8fabd04960bcf3b0 (diff)
downloadgdb-ed64e7e055ec09c7f30f00996407db8c414f6468.tar.gz
add HAVE_CONTINUABLE_WATCHPOINT to target_ops
Diffstat (limited to 'gdb/config/i386')
-rw-r--r--gdb/config/i386/nm-i386.h2
-rw-r--r--gdb/config/i386/nm-i386sco5.h2
-rw-r--r--gdb/config/i386/nm-i386sol2.h2
3 files changed, 3 insertions, 3 deletions
diff --git a/gdb/config/i386/nm-i386.h b/gdb/config/i386/nm-i386.h
index eed05a476fa..97a70539b0f 100644
--- a/gdb/config/i386/nm-i386.h
+++ b/gdb/config/i386/nm-i386.h
@@ -93,7 +93,7 @@ extern int i386_remove_hw_breakpoint (CORE_ADDR addr, void *shadow);
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. */
-#define HAVE_CONTINUABLE_WATCHPOINT
+#define HAVE_CONTINUABLE_WATCHPOINT 1
#define STOPPED_BY_WATCHPOINT(W) (i386_stopped_data_address () != 0)
diff --git a/gdb/config/i386/nm-i386sco5.h b/gdb/config/i386/nm-i386sco5.h
index 37a4b16d44b..65f317621e6 100644
--- a/gdb/config/i386/nm-i386sco5.h
+++ b/gdb/config/i386/nm-i386sco5.h
@@ -63,7 +63,7 @@ extern int kernel_u_size (void);
/* After a watchpoint trap, the PC points to the instruction which
caused the trap. But we can continue over it without disabling the
trap. */
-#define HAVE_CONTINUABLE_WATCHPOINT
+#define HAVE_CONTINUABLE_WATCHPOINT 1
#define HAVE_STEPPABLE_WATCHPOINT
#define STOPPED_BY_WATCHPOINT(W) \
diff --git a/gdb/config/i386/nm-i386sol2.h b/gdb/config/i386/nm-i386sol2.h
index 8a51942791f..aeb89a26f6f 100644
--- a/gdb/config/i386/nm-i386sol2.h
+++ b/gdb/config/i386/nm-i386sol2.h
@@ -32,7 +32,7 @@
/* When a hardware watchpoint fires off the PC will be left at the
instruction following the one which caused the watchpoint.
It will *NOT* be necessary for GDB to step over the watchpoint. */
-#define HAVE_CONTINUABLE_WATCHPOINT
+#define HAVE_CONTINUABLE_WATCHPOINT 1
/* Solaris x86 2.6 and 2.7 targets have a kernel bug when stepping
over an instruction that causes a page fault without triggering