From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: frame->unwind->this_base()
Date: Wed, 19 Mar 2003 14:11:00 -0000 [thread overview]
Message-ID: <20030319141142.GA20672@nevyn.them.org> (raw)
In-Reply-To: <3E777FF9.10005@redhat.com>
On Tue, Mar 18, 2003 at 03:22:17PM -0500, Andrew Cagney wrote:
> >On Tue, Mar 18, 2003 at 12:28:47PM -0500, Andrew Cagney wrote:
> >
> >>>That would be a very bad assumption. They are pratically guarenteed to
> >
> >>>>be different.
> >
> >>>
> >>>
> >>>Then what do you mean by a "dwarf2 frame"? I'd assume you meant the
> >>>CFA, but it sounds like you mean a frame for which we have dwarf2
> >>>.debug_info.
> >
> >>
> >>A frame with debug info provided by dwarf2. CFI gives the register
> >>info, location expressions give the variable info, ...
> >>
> >>What started out as a simple cfi-frame looks like it might need to
> >>evolve into dwarf2-frame ...
> >
> >
> >DWARF-2 debug info does not corelate with CFI info. For instance, GCC
> >will generate DWARF-2 CFI with stabs debug info. It will also generate
> >CFI with no debug info at all, or DWARF-2 info without any CFI (if
> >requested).
>
> True dwarf2 debug info or that .eh_frame stuff (i'm curious)?
Hmm, I thought it would write out .debug_frame without DWARF-2 but
peering at the GCC source I seem to be wrong again. So just .eh_frame.
In any case, we'll parse both, so I stand by my statement. We'll have
.eh_frame even without normal debug info.
> For stabs to work, it needs FRAME_LOCALS_ADDRESS(); and
> FRAME_LOCALS_ADDRESS() relies on the prologue analyzer (since frame ID
> won't correspond to `frame-base') for the computation of the correct
> value; and that means unwinding the same frame two ways. Outch.
Yeah...
- if we have CFI use it to find the frame address. Does this
become the frame ID?
- if we have dwarf2 debug and CFI, then we don't need to do prologue
analysis; CFI should give us everything we need
- if we have stabs debug and CFI, then we do need to do prologue
analysis to get FRAME_LOCALS_ADDRESS
- if we have either kind of debug info and no CFI then we need to do
prologue analysis; for dwarf2 we'll also need to calculate the frame
base from DW_AT_frame_base in order to use it to find locals
Is that about right?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-19 14:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-16 22:04 frame->unwind->this_base() Andrew Cagney
2003-03-16 22:10 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-17 0:09 ` frame->unwind->this_base() Andrew Cagney
2003-03-17 0:14 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-17 16:22 ` frame->unwind->this_base() Andrew Cagney
2003-03-17 16:38 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-17 16:56 ` frame->unwind->this_base() Andrew Cagney
2003-03-17 17:11 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-17 18:20 ` frame->unwind->this_base() Andrew Cagney
2003-03-17 19:35 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-18 4:29 ` frame->unwind->this_base() Andrew Cagney
2003-03-18 5:13 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-18 15:22 ` frame->unwind->this_base() Andrew Cagney
2003-03-18 16:38 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-18 17:02 ` frame->unwind->this_base() Andrew Cagney
2003-03-18 17:11 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-18 17:28 ` frame->unwind->this_base() Andrew Cagney
2003-03-18 17:38 ` frame->unwind->this_base() Daniel Jacobowitz
2003-03-18 20:22 ` frame->unwind->this_base() Andrew Cagney
2003-03-19 14:11 ` Daniel Jacobowitz [this message]
2003-03-19 15:24 ` frame->unwind->this_base() Andrew Cagney
2003-03-19 15:32 ` frame->unwind->this_base() Daniel Jacobowitz
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=20030319141142.GA20672@nevyn.them.org \
--to=drow@mvista.com \
--cc=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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).