[patch] Move h/w watchpoints to 5.2. + misc

[Andrew Cagney <ac131313 at cygnus dot com>]

FYI,

Per my previous e-mail, the hardware watchpoint stuff that H.J. raised
is part of the 5.2 release criteria.  If it makes it in 5.1 then it is a
bonus.

	Andrew
Wed Nov  1 23:07:29 2000  Andrew Cagney  <cagney@b1.cygnus.com>

	* TODO: Document cleanup to function monitor.dumpregs.  Move
 	hardware watchpoint notes to 5.2.

Index: TODO
===================================================================
RCS file: /cvs/src/src/gdb/TODO,v
retrieving revision 1.51
diff -p -r1.51 TODO
*** TODO	2000/10/23 22:49:28	1.51
--- TODO	2000/11/01 12:26:40
*************** 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 ----
*************** Fix at least one thread bug.
*** 256,261 ****
--- 236,264 ----
  
  --
  
+ Hardware watchpint [sic] problems on x86 OSes, including Linux:
+ http://sources.redhat.com/ml/gdb/2000-09/msg00005.html
+ 
+ H.J. Lu writes:
+ 
+ 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.)
+ 
+ --
+ 
  		GDB 5.2 - New features
  		======================
  
*************** Rename read_register{,_pid}() to read_un
*** 801,806 ****
--- 804,813 ----
  
  --
  
+ Change monitor.h:struct monitor.dumpregs to a void function.
+ 
+ --
+ 
  			Symbol Support
  			==============
  
*************** an error (or is interrupted).
*** 1785,1790 ****
--- 1792,1799 ----
  
  Remove the range and type checking code and documentation, if not
  going to implement.
+ 
+ --
  
  # Local Variables:
  # mode: text