mirror of
https://github.com/darlinghq/darling-gdb.git
synced 2024-11-24 12:39:59 +00:00
* gdbint.texinfo (Breakpoint Handling): Correct a double negative.
This commit is contained in:
parent
de18ac1fab
commit
50e3ee830c
@ -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).
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user