From: Jim Blandy <jimb@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Joel Brobecker <brobecker@gnat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFA] block_innermost_frame tweak
Date: Fri, 21 Jun 2002 12:14:00 -0000 [thread overview]
Message-ID: <np7kksv3zm.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <3D126D8A.9020908@cygnus.com>
Andrew Cagney <ac131313@cygnus.com> writes:
> Is there a better name? As you note, it isn't a valid PC (it may not
> even point into an instruction!). Further, it is isn't the address of
> the instruction ``calling'' the ``frame''. Last time this came up
> address_in_block() was used - frame_address_in_block()?
I don't disagree with your objections (raised in a previous
discussion) that `frame->pc - 1' isn't a proper PC. It may never have
been the value of the PC register (if indeed the architecture has a
register named `PC'); it doesn't even necessarily point to an
instruction.
That said, I feel that replacing "PC" with just "address" actually
makes matters worse, not better. It's very helpful to see at a glance
that a particular CORE_ADDR value is a pointer into the instruction
stream. The exact semantics of the value --- is this the return
address or the address of the call? do we need to apply
DECR_PC_AFTER_BREAK? and so on --- is something that one uncovers
when one researches the value more carefully, as with anything else.
But if I'm the only one who has this reaction, then I don't mind the
renaming.
Is there some third terse term that indicates (or could indicate, by
establishing a convention) "pointer into the instruction stream that
isn't necessarily an instruction address or the value of a register"?
next prev parent reply other threads:[~2002-06-21 19:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-20 13:14 Joel Brobecker
2002-06-20 14:09 ` Jim Blandy
2002-06-20 15:21 ` Joel Brobecker
2002-06-20 17:04 ` Andrew Cagney
2002-06-21 10:31 ` Joel Brobecker
2002-06-21 12:14 ` Jim Blandy [this message]
2002-06-21 13:24 ` Andrew Cagney
2002-06-21 15:33 ` Jim Blandy
2002-06-21 15:55 ` Andrew Cagney
2002-06-21 16:22 ` Jim Blandy
2002-07-02 10:41 ` Joel Brobecker
2002-07-02 11:05 ` Jim Blandy
2002-07-02 12:12 ` Joel Brobecker
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=np7kksv3zm.fsf@zwingli.cygnus.com \
--to=jimb@redhat.com \
--cc=ac131313@cygnus.com \
--cc=brobecker@gnat.com \
--cc=gdb-patches@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