From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Berlin <dan@www.cgsoftware.com>
Cc: gdb@sources.redhat.com
Subject: Re: Integrating DWARF2 CFA info
Date: Thu, 10 May 2001 10:04:00 -0000 [thread overview]
Message-ID: <3AFAC8BB.7040306@cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105101151430.9863-100000@www.cgsoftware.com>
> Well, actually, IMHO, it is.
> The CFA info gives us the location of all saved registers for the entire
> procedure.
> It's always correct, even in the presence of optimization.
> Given the pc for the frame, it can tell you exactly where all the saved
> registers are, at that particular point in time.
> Therefore, it is strictly better to use the CFA info, than scan the
> instructions.
>
> So I see a strict hiearchy of what to use:
> Dwarf2 CFA Info
> <whatever else>
This assumes that dwarf2 info is more correct than some other sort of info.
Andrew
next prev parent reply other threads:[~2001-05-10 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 12:08 Daniel Berlin
2001-05-10 8:33 ` Andrew Cagney
2001-05-10 8:57 ` Daniel Berlin
2001-05-10 10:04 ` Andrew Cagney [this message]
2001-05-10 11:07 ` Daniel Berlin
2001-05-10 11:19 ` Daniel Berlin
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=3AFAC8BB.7040306@cygnus.com \
--to=ac131313@cygnus.com \
--cc=dan@www.cgsoftware.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