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

* gdb.texinfo: document `set remotedebug' and `set rstack_high_address'.

This commit is contained in:
John Gilmore 1992-06-20 23:32:18 +00:00
parent b4fde6fa65
commit d8a68b2844
2 changed files with 31 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@ -1,3 +1,8 @@
Sat Jun 20 16:31:10 1992 John Gilmore (gnu at cygnus.com)
* gdb.texinfo: document `set remotedebug' and `set
rstack_high_address'.
Thu May 14 17:09:48 1992 Roland H. Pesch (pesch@fowanton.cygnus.com)
* gdb.texinfo: slight expansion of new text on reading info files

26
gdb/doc/gdb.texinfo
View File

@ -4321,6 +4321,24 @@ code generated by your compiler. If some registers are not saved, or if
_GDBN__ is unable to locate the saved registers, the selected stack
frame will make no difference.
_if__(_AMD29K__)
@item set rstack_high_address @var{address}
@kindex set rstack_high_address
@cindex AMD 29K
On AMD 29000 family processors, registers are saved in a separate ``register
stack''. There is no way for GDB to determine the extent of this stack.
Normally, GDB just assumes that the stack is ``large enough''.
This may result in GDB referencing memory locations that don't
exist, you can specify the ending address of the register stack with the
@code{set rstack_high_address} command. The argument should be an address,
which you will probably want to precede with 0x and specify in hexadecimal.
@item show rstack_high_address
@kindex show rstack_high_address
@cindex AMD 29K
Display the current limit of the register stack.
_fi__(_AMD29K__)
@node Floating Point Hardware, , Registers, Data
@section Floating Point Hardware
@cindex floating point
@ -6421,6 +6439,14 @@ step and continue the remote program.
To resume the remote program and stop debugging it, use the @code{detach}
command.
@kindex set remotedebug
@kindex show remotedebug
If you have trouble with the serial connection, you can use the
command @code{set remotedebug}. This causes all packets sent back
and forth across the serial line to be reported to GDB's standard output.
@code{set remotedebug off} turns it off, and @code{show remotedebug} will
show you its current state.
Other remote targets may be available in your
configuration of GDB; use @code{help targets} to list them.