diff options
| author | Theodore A. Roth <troth@openavr.org> | 2003-05-14 20:29:15 +0000 |
|---|---|---|
| committer | Theodore A. Roth <troth@openavr.org> | 2003-05-14 20:29:15 +0000 |
| commit | 50e3ee830c22f8b63b6eebee36cee465261386aa (patch) | |
| tree | b3e704cb0223c33ddf2278e4735a0e964cbdfb27 /gdb/doc/gdbint.texinfo | |
| parent | de18ac1fab2bdc3d94c6a0b8fff01566890cfeda (diff) | |
| download | gdb-50e3ee830c22f8b63b6eebee36cee465261386aa.zip gdb-50e3ee830c22f8b63b6eebee36cee465261386aa.tar.gz gdb-50e3ee830c22f8b63b6eebee36cee465261386aa.tar.bz2 | |
* gdbint.texinfo (Breakpoint Handling): Correct a double negative.
Diffstat (limited to 'gdb/doc/gdbint.texinfo')
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 2 |
1 files changed, 1 insertions, 1 deletions
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 |