Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: <gdb@sources.redhat.com>
Subject: Re: View registers from stack frames
Date: Fri, 08 Oct 2004 10:14:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20041008105008.01d72828@NT_SERVER> (raw)
In-Reply-To: <20041007085738.45b5b55a@saguaro>


>> In frame 0 pc and lr are correct (different), but in the other frames
>> they always have the same value whereas lr should have the
>> value of the pc of the next frame, right?
>
>Recent versions of GDB show the same value for lr and pc for the later
>frames.  I think this is okay.
>
>Kevin

I have only tested the --target=powerpc-eabi version so I don't know about
other processors. Is this true that gdb is supposed to show pc and lr with
the same values for stack frames >0? Isn't the purpose of the lr to point
to the previous stack frame (and so be different from the actual pc)?
And if the actual behaviour is correct then why is it different for frame 0?

Thanks

bye  Fabi



       reply	other threads:[~2004-10-08  8:54 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 [this message]
2004-10-11 19:16     ` Kevin Buettner
2004-10-12 14:03       ` Fabian Cenedese
2004-10-16 15:11         ` Kevin Buettner
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=5.2.0.9.1.20041008105008.01d72828@NT_SERVER \
    --to=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