aboutsummaryrefslogtreecommitdiff
path: root/gdb/TODO
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2001-02-16 22:59:48 +0000
committerAndrew Cagney <cagney@redhat.com>2001-02-16 22:59:48 +0000
commit0a9c3cb62aaac5cb470a8aec2507fb214b6dd5c8 (patch)
treeaba01057d68bf7d1bca4045fbadb02aa6ab1a04f /gdb/TODO
parent2ef048fc9fe85293e7cb3aa8259ab0a60bcedb1b (diff)
downloadgdb-0a9c3cb62aaac5cb470a8aec2507fb214b6dd5c8.zip
gdb-0a9c3cb62aaac5cb470a8aec2507fb214b6dd5c8.tar.gz
gdb-0a9c3cb62aaac5cb470a8aec2507fb214b6dd5c8.tar.bz2
Move hardware stuff to not 5.1 - changelog already committed.
Diffstat (limited to 'gdb/TODO')
-rw-r--r--gdb/TODO40
1 files changed, 20 insertions, 20 deletions
diff --git a/gdb/TODO b/gdb/TODO
index 83c0c44..acca85a 100644
--- a/gdb/TODO
+++ b/gdb/TODO
@@ -12,26 +12,6 @@ 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
@@ -542,6 +522,26 @@ fundamental architectural change.
--
+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.)
+
+--
+
Add built-by, build-date, tm, xm, nm and anything else into gdb binary
so that you can see how the GDB was created.