diff options
| -rw-r--r-- | gdb/doc/gdb.texinfo | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 444b38a..9882beb 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -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} |