From: Andrew Cagney <ac131313@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH/i386newframe/RFC] DWARF CFI frame unwinder
Date: Mon, 05 May 2003 03:35:00 -0000 [thread overview]
Message-ID: <3EB5DBFF.6030009@redhat.com> (raw)
In-Reply-To: <200305042207.h44M7gNG023734@elgar.kettenis.dyndns.org>
Mark, fyi,
> + case REG_SAVED_REG:
> + *optimizedp = 0;
> + *lvalp = lval_register;
> + *addrp = 0;
> + *realnump = DWARF2_REG_TO_REGNUM (cache->reg[regnum].loc.reg);
> + if (valuep)
> + {
> + /* Read the value from the register. */
> + frame_unwind_register (next_frame, *realnump, valuep);
> + }
> + break;
> +
Set *addrp to the register offset hack (Otherwize something mysterious
fails. What? I don't remember).
Using the frame obstack for memory looks right.
> +static CORE_ADDR
> +dwarf_frame_base_address (struct frame_info *next_frame, void **this_cache)
> +{
> + struct dwarf_frame_cache *cache = dwarf_frame_cache (next_frame, this_cache);
> +
> + return cache->cfa;
> +}
This isn't right. It should return DW_AT_frame_base. However, since
dwarf2expr.c doesn't yet use these methods it doesn't [?] really matter.
Only affects ``info frame''.
I suspect things like execute_stack_op might need more cleanups. A dead
target, or bad memory read, can throw an error.
Looks like the interface works (and oh so much cleaner than the old
code) :-)
Andrew
next prev parent reply other threads:[~2003-05-05 3:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 22:07 Mark Kettenis
2003-05-05 3:35 ` Andrew Cagney [this message]
2003-05-05 3:42 ` Daniel Jacobowitz
2003-05-05 14:08 ` Andrew Cagney
2003-05-05 14:27 ` Daniel Jacobowitz
2003-05-05 14:52 ` Andrew Cagney
2003-05-05 14:59 ` Daniel Jacobowitz
2003-05-05 14:11 ` Mark Kettenis
2003-05-05 13:48 ` Mark Kettenis
2003-05-05 14:24 ` Andrew Cagney
2003-05-05 13:52 ` Mark Kettenis
2003-05-05 14:31 ` 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=3EB5DBFF.6030009@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kettenis@chello.nl \
/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