This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
[patch/todo] Move Move ``Hardware watchpint problems'' out of 5.1
- To: GDB Patches <gdb-patches at sourceware dot cygnus dot com>
- Subject: [patch/todo] Move Move ``Hardware watchpint problems'' out of 5.1
- From: Andrew Cagney <ac131313 at cygnus dot com>
- Date: Fri, 16 Feb 2001 12:38:46 -0500
FYI,
I've committed the attatched. This was snuck into the 5.1 release
criteria (and I should emphasise that the sneakering was not done by Eli
:-).
Doing this now is some what ironic as Eli has just turned his head
towards the problem and may well get it into 5.1!
I ment to do this months ago :-(
Andrew
2001-02-16 Andrew Cagney <ac131313@redhat.com>
* TODO (5.1): Move ``Hardware watchpint problems'' out of 5.1.
Index: TODO
===================================================================
RCS file: /cvs/src/src/gdb/TODO,v
retrieving revision 1.58
diff -p -r1.58 TODO
*** TODO 2001/02/08 06:03:52 1.58
--- TODO 2001/02/16 17:38:17
*************** cycle. People hope to have these proble
*** 12,37 ****
--
- 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
--- 12,17 ----
*************** coverage analysis).
*** 539,544 ****
--- 519,544 ----
These are harder than cleanups but easier than work involving
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.)
--