OpenE2K
/
binutils-gdb
12
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

> * gdb.texinfo (hbreak, watch): Fix typo, "date" -> "data".

This commit is contained in:
Fred Fish 1998-04-13 21:47:38 +00:00
parent 1e83118b79
commit 8387d6dfd3
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
gdb/doc/ChangeLog
View File

@ -1,3 +1,7 @@
Mon Apr 13 14:05:00 1998 Fred Fish <fnf@cygnus.com>
* gdb.texinfo (hbreak, watch): Fix typo, "date" -> "data".
Thu Apr 2 16:52:44 1998 Jason Molenda (crash@bugshack.cygnus.com)
* LRS: Reformat a bit to keep text under 80 columns.

4
gdb/doc/gdb.texinfo
View File

@ -2202,7 +2202,7 @@ have this support. The main purpose of this is EPROM/ROM code
debugging, so you can set a breakpoint at an instruction without
changing the instruction. This can be used with the new trap-generation
provided by SPARClite DSU. DSU will generate traps when a program accesses
some date or instruction address that is assigned to the debug registers.
some data or instruction address that is assigned to the debug registers.
However the hardware breakpoint registers can only take two data breakpoints,
and @value{GDBN} will reject this command if more than two are used.
Delete or disable usused hardware breakpoints before setting
@ -2356,7 +2356,7 @@ Set a watchpoint for an expression. @value{GDBN} will break when @var{expr}
is written into by the program and its value changes.
This can be used with the new trap-generation provided by
SPARClite DSU. DSU will generate traps when a program accesses
some date or instruction address that is assigned to the debug registers.
some data or instruction address that is assigned to the debug registers.
For the data addresses, DSU facilitates the @code{watch} command.
However the hardware breakpoint registers can only take two data watchpoints,
and both watchpoints must be the same kind. For example, you can set two