From: Andrew Cagney <ac131313@redhat.com>
To: gdb@sources.redhat.com
Subject: Enable frame-base before frame-unwind?
Date: Wed, 25 Jun 2003 16:51:00 -0000 [thread overview]
Message-ID: <3EF9C2F1.7040904@redhat.com> (raw)
Here's a new theory on how to migrate to the unwind code:
Enable frame-base before frame-unwind.
Why? The frame-unwind code can't be enabled until frame-base is working
anyway. Since frame-base is an almost direct replacement for
FRAME_LOCALS_ADDRESS and FRAME_ARGS_ADDRESS, and the return values for
the old/new methods are the same, I think getting frame-base working is
going to be much easier than getting frame-unwind working. Since
frame-base and frame-unwind share the prologue analysis code, debugging
it with the less harmful frame-base should make life easier.
Any one want to prove the theory?
Andrew
next reply other threads:[~2003-06-25 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 16:51 Andrew Cagney [this message]
2003-06-25 18:28 ` Daniel Jacobowitz
2003-06-26 4:56 ` Daniel Jacobowitz
2003-06-26 14:07 ` 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=3EF9C2F1.7040904@redhat.com \
--to=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