darkkirb/old-cross-binutils
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

More updates due to Picard refcard comments.

Browse source
This commit is contained in:
Roland Pesch 1991-10-16 22:08:33 +00:00
parent a3ae208f8a
commit 092678655c
1 changed files with 17 additions and 16 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

33
gdb/doc/gdb.texinfo
View file

@ -3928,8 +3928,13 @@ may be any register name valid on the machine you are using, with
or without the initial @samp{$}. or without the initial @samp{$}.
@end table @end table
The register names @code{$pc} and @code{$sp} are used on most machines _GDBN__ has four ``standard'' register names that are available (in
for the program counter register and the stack pointer. For example, expressions) on most machines---whenever they don't conflict with an
architecture's canonical mnemonics for registers. The register names
@code{$pc} and @code{$sp} are used for the program counter register and
the stack pointer. @code{$fp} is used for a register that contains a
pointer to the current stack frame, and @code{$ps} is used for a
register that contains the processor status. For example,
you could print the program counter in hex with you could print the program counter in hex with
@example @example
p/x $pc p/x $pc
@ -3942,24 +3947,20 @@ x/i $pc
@end example @end example
@noindent @noindent
or add four to the stack pointer with or add four to the stack pointer @footnote{This is a way of removing one
word from the stack, on machines where stacks grow downward in memory
(most machines, nowadays). This assumes that the innermost stack frame
is selected; setting @code{$sp} is not allowed when other stack frames
are selected. To pop entire frames off the stack, regardless of
machine architecture, use @code{return}; @pxref{Returning}.} with
@example @example
set $sp += 4 set $sp += 4
@end example @end example
@noindent Whenever possible, these four standard register names are available on
The last is a way of removing one word from the stack, on machines where your machine even though the machine has different canonical mnemonics,
stacks grow downward in memory (most machines, nowadays). This assumes so long as there is no conflict. The @code{info registers} command
that the innermost stack frame is selected; setting @code{$sp} is shows the canonical names. For example, on the SPARC, @code{info
not allowed when other stack frames are selected. (To pop entire frames
off the stack, regardless of machine architecture, use @code{return};
@pxref{Returning}.)
Often @code{$fp} is used for a register that contains a pointer to the
current stack frame, and @code{$ps} is sometimes used for a register
that contains the processor status. These standard register names may
be available on your machine even though the @code{info registers}
command shows other names. For example, on the SPARC, @code{info
registers} displays the processor status register as @code{$psr} but you registers} displays the processor status register as @code{$psr} but you
can also refer to it as @code{$ps}. can also refer to it as @code{$ps}.