From: Andrew Cagney <ac131313@cygnus.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: ARM frame fp is not always FP_REGNUM
Date: Mon, 03 Jul 2000 22:39:00 -0000 [thread overview]
Message-ID: <39617827.29D15730@cygnus.com> (raw)
In-Reply-To: <orn1jyfpso.fsf@guarana.lsd.ic.unicamp.br>
Alexandre Oliva wrote:
>
> read_relative_register_raw_bytes_for_frame() would optimize access to
> FP_REGNUM by not re-reading it when the value of FP is already known.
> However, because FP is not always available, sometimes the value of SP
> is stored in the frame structure as the value of FP. In this case,
> reading the value of FP_REGNUM will get you SP instead of the actual
> value of the FP register. This patch fixes this bug. Ok to install?
I'm not sure about this.
FP_REGNUM refers to GDB's internal frame-handle / frame-pointer /
frame-base variable. It doesn't refer to the ISA register that is seen
in architectures such as ARM or VAX. Unfortunatly, some architectures
have both and this leads to confusion.
What exactly is the behavour you're seeing and what behavour are you
trying to achieve.
Andrew
From aoliva@redhat.com Mon Jul 03 22:53:00 2000
From: Alexandre Oliva <aoliva@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: ARM frame fp is not always FP_REGNUM
Date: Mon, 03 Jul 2000 22:53:00 -0000
Message-id: <or1z1afnle.fsf@guarana.lsd.ic.unicamp.br>
References: <orn1jyfpso.fsf@guarana.lsd.ic.unicamp.br> <39617827.29D15730@cygnus.com>
X-SW-Source: 2000-07/msg00021.html
Content-length: 673
On Jul 4, 2000, Andrew Cagney <ac131313@cygnus.com> wrote:
> FP_REGNUM refers to GDB's internal frame-handle / frame-pointer /
> frame-base variable.
On ARM, it's register 11, which is a real register. But SP_REGNUM is
register 13. Then, when framereg == 13 in EXTRA_FRAME_INFO, `info
regs' will display the value of r13 for r11, and the actual value of
r11 cannot be obtained.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next parent reply other threads:[~2000-07-03 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <orn1jyfpso.fsf@guarana.lsd.ic.unicamp.br>
2000-07-03 22:39 ` Andrew Cagney [this message]
[not found] ` <or1z1afnle.fsf@guarana.lsd.ic.unicamp.br>
2000-07-04 0:29 ` Andrew Cagney
[not found] ` <oru2e6cpaz.fsf@guarana.lsd.ic.unicamp.br>
2000-07-04 1:09 ` Andrew Cagney
2000-07-04 8:56 ` Michael Snyder
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=39617827.29D15730@cygnus.com \
--to=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=gdb-patches@sourceware.cygnus.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