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 do not exist. If necessary, you can get around
this problem by specifying the ending address of the register stack with
the set rstack_high_address command. The argument should be an
address, which you probably want to precede with `0x' to specify in
hexadecimal.
show rstack_high_address
Display the current limit of the register stack, on AMD 29000 family
processors.
Debugging with GDB