Re: View registers from stack frames

[Daniel Jacobowitz <drow@false.org>]

On Tue, Oct 05, 2004 at 03:53:22PM +0200, Fabian Cenedese wrote:
> 
> >>With the stack commands (frame, up, down) I can select a different
> >>stack frame. Local variables and arguments (even with same name)
> >>have different values, depending on the stack frame number. But it
> >>seems that registers aren't corrected for previous stack frames. Is
> >>this correct? e.g. the PC and LR should change their value on every
> >>frame, and the PC was the last LR. But "info reg" always shows the
> >>same values. Is there any way to get the previous frame's registers?
> >>When I do "info frame x" I get something like "saved pc 0x..." so at
> >>least this information is available, why isn't this put into the register
> >>overview? And what about the other SPRs and GPRs?
> >
> >You've just described the expected and correct behavior.  That makes it sound like an architecture specific bug.  Which architecture system is this on, and can you post a transcript.
> 
> I'm using a self built gdb-6.1.1 for PPC-targets and cygwin. The
> communication with the target is over a stub-server to a PPC-board.

For PPC, try 6.2 instead.

> My question is: why do pc and lr (and all other registers) always show the same
> value even if I have selected another stack frame? I would have expected that pc
> changes to 0x60564 in frame 1 and 0x60408 in frame 2, lr likewise to 0x60408
> in frame 1 and 0x8c8a8 in frame 2. Why is this not the case? That's a little bit
> misleading. I would like not only to see variables and arguments in previous
> frames but also the registers.

As Andrew already explained, this is what is supposed to happen.  It
did not used to work but was fixed by the new frame architecture.

-- 
Daniel Jacobowitz