From: Kevin Buettner <kevinb@redhat.com>
To: Fabian Cenedese <Cenedese@indel.ch>
Cc: <gdb@sources.redhat.com>
Subject: Re: View registers from stack frames
Date: Sat, 16 Oct 2004 15:11:00 -0000 [thread overview]
Message-ID: <20041015153348.0085e482@saguaro> (raw)
In-Reply-To: <5.2.0.9.1.20041012085225.01cecd88@NT_SERVER>
On Tue, 12 Oct 2004 08:56:40 +0200
Fabian Cenedese <Cenedese@indel.ch> wrote:
> >Looking at it another way, the reason that PC and LR are the same
> >value for frames other than the topmost frame (excluding possible
> >sigtramp frames, where they may in fact be different), is because LR
> >changes over the lifetime of the function. GDB is reporting this as
> >accurately as it can.
>
> Thanks for your extensive explanation, it looks more clear now why
> it is the way it is. The value I assumed to be in LR (PC in last frame)
> is still reported from gdb as "saved PC". Is there another possibility
> to get this value than the stack frame info? Is this maybe stored in
> some gdb internal variable?
From the stack? If I'm not mistaken, the saved LR value should be at
$sp+4.
I'm not aware of any GDB internal variables which hold this value.
Kevin
next prev parent reply other threads:[~2004-10-15 22:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5.2.0.9.1.20041007134711.01d12d90@NT_SERVER>
[not found] ` <20041007085738.45b5b55a@saguaro>
2004-10-08 10:14 ` Fabian Cenedese
2004-10-11 19:16 ` Kevin Buettner
2004-10-12 14:03 ` Fabian Cenedese
2004-10-16 15:11 ` Kevin Buettner [this message]
2004-10-07 17:50 Xinan Tang
-- strict thread matches above, loose matches on Subject: below --
2004-10-05 12:48 Fabian Cenedese
2004-10-05 13:30 ` Andrew Cagney
2004-10-05 14:02 ` Fabian Cenedese
2004-10-05 14:03 ` Daniel Jacobowitz
2004-10-05 15:00 ` Fabian Cenedese
2004-10-05 17:57 ` Fabian Cenedese
2004-10-06 1:57 ` Andrew Cagney
2004-10-06 7:18 ` Fabian Cenedese
2004-10-06 16:41 ` Kevin Buettner
2004-10-07 9:04 ` Fabian Cenedese
2004-10-11 19:21 ` Kevin Buettner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041015153348.0085e482@saguaro \
--to=kevinb@redhat.com \
--cc=Cenedese@indel.ch \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox