2000-09-06 H.J. Lu <hjl@gnu.org>

	* TODO: Add hardware watchpint problems on x86 OSes for 5.1.

diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4b28f5b580a41d7a4d56e82ee4ec3be2032c716a..9154e420583dc6c9caab775964b1d9add0b152f9 100644 (file)
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2000-09-06  H.J. Lu  <hjl@gnu.org>
+
+       * TODO: Add hardware watchpint problems on x86 OSes for 5.1.
+
 2000-09-06  Kevin Buettner  <kevinb@redhat.com>
 
        * ia64-tdep.c (examine_prologue): Add rotating register rename

diff --git a/gdb/TODO b/gdb/TODO
index c0931bef294fb2523b5f8d5d7bbd004dba6014c4..a6247ca1f49ac93f961c7d22450f7fe8f2582963 100644 (file)
--- a/gdb/TODO
+++ b/gdb/TODO
@@ -12,6 +12,26 @@ cycle.  People hope to have these problems fixed in 5.1.
 
 --
 
+Hardware watchpint problems on x86 OSes, including Linux:
+
+1. Delete/disable hardware watchpoints should free hardware debug
+registers. 
+2. Watch for different values on a viariable with one hardware debug
+register.
+
+According to Eli Zaretskii <eliz@delorie.com>:
+
+These are not GDB/ia32 issues per se: the above features are all
+implemented in the DJGPP port of GDB and work in v5.0.  Every
+x86-based target should be able to lift the relevant parts of
+go32-nat.c and use them almost verbatim.  You get debug register
+sharing through reference counts, and the ability to watch large
+regions (up to 16 bytes) using multiple registers.  (The required
+infrastructure in high-level GDB application code, mostly in
+breakpoint.c, is also working since v5.0.)
+
+--
+
 RFD: infrun.c: No bpstat_stop_status call after proceed over break?
 http://sourceware.cygnus.com/ml/gdb-patches/2000-q1/msg00665.html