From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: christophe.lyon@st.com, gdb@sources.redhat.com
Subject: Re: dwarf2 frame unwinder assumptions on SP
Date: Mon, 11 Jul 2005 19:47:00 -0000 [thread overview]
Message-ID: <200507111947.j6BJl7PV008162@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050711160334.GA31890@nevyn.them.org> (message from Daniel Jacobowitz on Mon, 11 Jul 2005 12:03:34 -0400)
Date: Mon, 11 Jul 2005 12:03:34 -0400
From: Daniel Jacobowitz <drow@false.org>
On Mon, Jul 11, 2005 at 05:58:14PM +0200, Christophe LYON wrote:
> I don't see what to do in init_reg without adding a new value to the
> dwarf2_frame_reg_rule enum. Do you mean changing the semantics of
> DWARF2_FRAME_REG_CFA and provide a frame_prev_register() method
> to interpret it accordingly?
No. Change it globally in dwarf2-frame.c, since the offset field is
currently unused with that rule.
It's probably better to introduce DWARF2_FRAME_REG_CFA_OFFSET just
like we did for DWARF2_FRAME_REG_RA_OFFSET. That would be #1 on your
list, Christophe.
I have the nagging feeling this has come up before, but I can't
remember the conclusion.
In the past we have discussed the relation between DW_OP_fbreg and
CFA; some GCC port was never defining the frame base, and someone
tried to use CFA. The conclusion then was that the CFA is defined
only for the call frame info. This is why #4 on Christophe's list
isn't the way to go.
Mark
next prev parent reply other threads:[~2005-07-11 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 14:44 Christophe LYON
2005-07-11 14:51 ` Daniel Jacobowitz
2005-07-11 15:33 ` Christophe LYON
2005-07-11 15:47 ` Daniel Jacobowitz
2005-07-11 15:58 ` Christophe LYON
2005-07-11 16:03 ` Daniel Jacobowitz
2005-07-11 17:02 ` Richard Henderson
2005-07-11 17:06 ` Daniel Jacobowitz
2005-07-11 19:47 ` Mark Kettenis [this message]
2005-07-12 14:05 ` Christophe LYON
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=200507111947.j6BJl7PV008162@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=christophe.lyon@st.com \
--cc=drow@false.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).