aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorH.J. Lu <hjl.tools@gmail.com>2000-09-06 15:23:04 +0000
committerH.J. Lu <hjl.tools@gmail.com>2000-09-06 15:23:04 +0000
commit967110cb4f8323e7fcb7578461fa8054fea8bbbc (patch)
tree8229b9679e8e4e85a4cedbb3596bffb3e0402866 /gdb
parent17a94bb6ec10dde8ab82261b469871fb55a559b5 (diff)
downloadgdb-967110cb4f8323e7fcb7578461fa8054fea8bbbc.zip
gdb-967110cb4f8323e7fcb7578461fa8054fea8bbbc.tar.gz
gdb-967110cb4f8323e7fcb7578461fa8054fea8bbbc.tar.bz2
2000-09-06 H.J. Lu <hjl@gnu.org>
* TODO: Add hardware watchpint problems on x86 OSes for 5.1.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/ChangeLog4
-rw-r--r--gdb/TODO20
2 files changed, 24 insertions, 0 deletions
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4b28f5b..9154e42 100644
--- 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 c0931be..a6247ca 100644
--- 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