aboutsummaryrefslogtreecommitdiff
path: root/gdb/TODO
diff options
context:
space:
mode:
authorAndrew Cagney <cagney@redhat.com>2000-08-04 09:32:19 +0000
committerAndrew Cagney <cagney@redhat.com>2000-08-04 09:32:19 +0000
commitd471ea57abff7347483577a42a061e3641c47461 (patch)
tree18ee894386472f42c6a0627292b1ab0b36ee751f /gdb/TODO
parent6688f7e9abbb806f7f90da6a8f1e283b4d0d21e6 (diff)
downloadgdb-d471ea57abff7347483577a42a061e3641c47461.zip
gdb-d471ea57abff7347483577a42a061e3641c47461.tar.gz
gdb-d471ea57abff7347483577a42a061e3641c47461.tar.bz2
Re-implement ``set/show remote Z-packet ...'' commands so that each Z
packet sub-type can be explicitly controled.
Diffstat (limited to 'gdb/TODO')
-rw-r--r--gdb/TODO12
1 files changed, 6 insertions, 6 deletions
diff --git a/gdb/TODO b/gdb/TODO
index 17b6451..633ac79 100644
--- a/gdb/TODO
+++ b/gdb/TODO
@@ -498,6 +498,11 @@ SIM_SIGBREAK and have GDB pass back sim_resume (..., SIGBREAK).
--
+Move remote_remove_hw_breakpoint, remote_insert_hw_breakpoint,
+remote_remove_watchpoint, remote_insert_watchpoint into target vector.
+
+--
+
New Features and Fixes
======================
@@ -751,7 +756,7 @@ ignored and a timeout is required before GDB retries. A pre-cursor to
fixing this this is making GDB's remote protocol packet more robust.
While downloading to a remote protocol target, gdb ignores packet
-errors in so far as it will continue to edownload with chunk N+1 even
+errors in so far as it will continue to download with chunk N+1 even
if chunk N was not correctly sent. This causes gdb.base/remote.exp to
take a painfully long time to run. As a PS that test needs to be
fixed so that it builds on 16 bit machines.
@@ -776,11 +781,6 @@ target endianess changes gdb doesn't know.
--
-Use the recently added add_set_auto_boolean_cmd() function to
-implement the X-packet commands.
-
---
-
Rename read_register{,_pid}() to read_unsigned_register{,_pid}().
--