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

(1) fix macro invocation of _GDBN__ that didn't expand due to adjacent 's';

Browse Source 
(2) attempt better text for when register relativization makes no diff.
This commit is contained in:
Roland Pesch 1991-04-04 00:33:18 +00:00
parent 5e4fd5d583
commit 8922ff76e3
1 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
gdb/doc/gdb.texinfo
View File

@ -3432,17 +3432,16 @@ cases, _GDBN__ normally works with the virtual format only (the format that
makes sense for your program), but the @samp{info registers} command
prints the data in both formats.
Register values are relative to the selected stack frame
Normally, register values are relative to the selected stack frame
(@pxref{Selection}). This means that you get the value that the register
would contain if all stack frames farther in were exited and their saved
registers restored. In order to see the contents of hardware registers,
you must select the innermost frame (with @samp{frame 0}).
Some registers are never saved (typically those numbered zero or one)
because they are used for returning function values. In some operating
systems (those using the ``caller saves'' convention), there are other
registers intended for free alteration by a called routine. For these
registers, relativization makes no difference.
However, _GDBN__ must deduce where registers are saved, from the machine
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.
@table @code
@item info registers
@ -4183,7 +4182,7 @@ _GDBN__ indicates its readiness to read a command by printing a string
called the @dfn{prompt}. This string is normally @samp{(_GDBP__)}. You can
change the prompt string with the @samp{set prompt} command. For
instance, when debugging _GDBN__ with _GDBN__, it is useful to change the prompt
in one of the _GDBN__s so that you tell which one you are talking to.
in one of the _GDBN__<>s so that you tell which one you are talking to.
@table @code
@item set prompt @var{newprompt}