aboutsummaryrefslogtreecommitdiff
path: root/gdb
diff options
context:
space:
mode:
authorTheodore A. Roth <troth@openavr.org>2003-05-14 20:29:15 +0000
committerTheodore A. Roth <troth@openavr.org>2003-05-14 20:29:15 +0000
commit50e3ee830c22f8b63b6eebee36cee465261386aa (patch)
treeb3e704cb0223c33ddf2278e4735a0e964cbdfb27 /gdb
parentde18ac1fab2bdc3d94c6a0b8fff01566890cfeda (diff)
downloadgdb-50e3ee830c22f8b63b6eebee36cee465261386aa.zip
gdb-50e3ee830c22f8b63b6eebee36cee465261386aa.tar.gz
gdb-50e3ee830c22f8b63b6eebee36cee465261386aa.tar.bz2
* gdbint.texinfo (Breakpoint Handling): Correct a double negative.
Diffstat (limited to 'gdb')
-rw-r--r--gdb/doc/ChangeLog4
-rw-r--r--gdb/doc/gdbint.texinfo2
2 files changed, 5 insertions, 1 deletions
diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog
index f8e992d..ba39d42 100644
--- a/gdb/doc/ChangeLog
+++ b/gdb/doc/ChangeLog
@@ -1,3 +1,7 @@
+2003-05-14 Theodore A. Roth <troth@openavr.org>
+
+ * gdbint.texinfo (Breakpoint Handling): Correct a double negative.
+
2003-05-10 H.J. Lu <hongjiu.lu@intel.com>
* Makefile.in (gdb-cfg.texi): Replace $$LN_S with $(LN_S).
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo
index 28cdc82..12bd404 100644
--- a/gdb/doc/gdbint.texinfo
+++ b/gdb/doc/gdbint.texinfo
@@ -288,7 +288,7 @@ A third possibility is that the target already has the ability to do
breakpoints somehow; for instance, a ROM monitor may do its own
software breakpoints. So although these are not literally ``hardware
breakpoints'', from @value{GDBN}'s point of view they work the same;
-@value{GDBN} need not do nothing more than set the breakpoint and wait
+@value{GDBN} need not do anything more than set the breakpoint and wait
for something to happen.
Since they depend on hardware resources, hardware breakpoints may be