From: "Paul N. Hilfinger" <hilfingr@otisco.mckusick.com>
To: ac131313@redhat.com
Cc: gdb@sources.redhat.com
Subject: Discrepency between gdbarch_frame_locals_address and get_frame_locals_address?
Date: Mon, 23 Jun 2003 19:02:00 -0000 [thread overview]
Message-ID: <200306231902.h5NJ2Us00812@otisco.McKusick.COM> (raw)
In-Reply-To: <3EF62D05.8070205@redhat.com>
Andrew,
Whilst poking around on related things, I observed that, at least on
Linux, the values of gdbarch_frame_locals_address and
get_frame_locals_address disagree. The latter appears to be correct,
since it is used in read_var_value in what I assume is the intended
way (add SYMBOL_VALUE to get_frame_locals_address (frame) to get
variable address). Would you like a patch, or is there a subtle
point here that I am missing?
Thanks.
Paul
next prev parent reply other threads:[~2003-06-23 19:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 22:26 Always cache memory and registers Andrew Cagney
2003-06-22 22:34 ` Daniel Jacobowitz
2003-06-22 22:55 ` Andrew Cagney
2003-06-23 3:57 ` Daniel Jacobowitz
2003-06-23 14:13 ` Andrew Cagney
2003-06-23 19:02 ` Paul N. Hilfinger [this message]
2003-06-23 19:47 ` Discrepency between gdbarch_frame_locals_address and get_frame_locals_address? Andrew Cagney
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=200306231902.h5NJ2Us00812@otisco.McKusick.COM \
--to=hilfingr@otisco.mckusick.com \
--cc=Hilfinger@otisco.mckusick.com \
--cc=ac131313@redhat.com \
--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