From: Andrew Cagney Date: Fri, 16 Feb 2001 22:59:48 +0000 (+0000) Subject: Move hardware stuff to not 5.1 - changelog already committed. X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=0a9c3cb62aaac5cb470a8aec2507fb214b6dd5c8;p=binutils-gdb.git Move hardware stuff to not 5.1 - changelog already committed. --- diff --git a/gdb/TODO b/gdb/TODO index 83c0c4476a8..acca85a7280 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 : - -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 : + +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.