From: Michael Snyder <msnyder@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: Re: [rfc] ``pc'' -> resume_addr?
Date: Thu, 11 Apr 2002 17:39:00 -0000 [thread overview]
Message-ID: <3CB62A0B.AFA5623B@redhat.com> (raw)
In-Reply-To: <1020411234158.ZM4406@localhost.localdomain>
Kevin Buettner wrote:
>
> On Apr 11, 6:16pm, Andrew Cagney wrote:
>
> > >> I think this name choice was unfortunate. It is too easy for a
> > >> developer to confuse ``pc'' with the hardware ``pc''.
> > >
> > > Could you please explain further why you think the name choice was
> > > unfortunate?
> >
> > I think the name ``pc'' brings with it a certain amount of baggage.
> > When reading a piece of code, it isn't clear if the hardware ``pc''
> > (possibly needing adjustment) or the program's resume address is being used.
>
> Is there really that much confusion about this though? I think that
> the length of time during which this confusion exists is mercifully
> brief. AFAICT, gdb's notion of the pc is adjusted shortly after
> stopping via a call to bpstat_stop_status() and from then on, the pc
> value is simply the continuation (or resume) address. Even the "PC"
> value in the register cache has been adjusted to be the program's
> resume address at this point.
And since the register cache is write-thru, so has the child's PC
register.
next prev parent reply other threads:[~2002-04-12 0:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 13:38 Andrew Cagney
2002-04-11 13:58 ` Kevin Buettner
2002-04-11 15:15 ` Andrew Cagney
2002-04-11 16:35 ` Andrew Cagney
2002-04-11 16:48 ` Kevin Buettner
2002-04-11 17:08 ` Andrew Cagney
2002-04-11 17:37 ` Michael Snyder
2002-04-11 16:42 ` Kevin Buettner
2002-04-11 17:39 ` Michael Snyder [this message]
2002-04-11 17:34 ` Michael Snyder
2002-04-12 8:59 ` Andrew Cagney
2002-04-13 20:21 ` Andrew Cagney
2002-04-11 17:25 ` Michael Snyder
2002-04-26 8:09 ` 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=3CB62A0B.AFA5623B@redhat.com \
--to=msnyder@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@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