Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: gdb@sources.redhat.com
Subject: [rfc] Add per frame frame_saved_pc()
Date: Thu, 19 Sep 2002 20:30:00 -0000	[thread overview]
Message-ID: <3D8A9662.1080902@ges.redhat.com> (raw)

Hello,

Back to (trumpet noises) CFI and more fall-out from the MIPS and generic 
dummy frames.

- The CFI doco describes a ``return_address_register'' which ``[...] 
might not correspond to a machine register''.  This means a CFI specific 
frame saved PC method.

- Given a generic dummy frame, it knows exactly where the callers frame 
PC is.  No need to ask the target code.

With this in mind, I'd like to propose making frame_saved_pc() a 
per-frame method.

Thoughts?

To be honest, it is largely motivated by me having to wade though the 
MIPS code and add if(PC_IN_CALL_DUMMY()) to everything - I'm hopeing to 
avoid it next time :-)

After this is comes FRAME_CHAIN() but I think that needs more careful 
consideration.

Andrew


             reply	other threads:[~2002-09-20  3:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-19 20:30 Andrew Cagney [this message]
2002-09-20  0:24 ` Kevin Buettner
2002-09-20  8:11   ` Andrew Cagney
2002-09-21 18:08     ` 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=3D8A9662.1080902@ges.redhat.com \
    --to=ac131313@ges.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