From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: frame->unwind->this_base()
Date: Tue, 18 Mar 2003 17:38:00 -0000 [thread overview]
Message-ID: <20030318173814.GA28471@nevyn.them.org> (raw)
In-Reply-To: <3E77574F.2010407@redhat.com>
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).
Can't lump 'em that way.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-03-18 17:38 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 ` Daniel Jacobowitz [this message]
2003-03-18 20:22 ` frame->unwind->this_base() Andrew Cagney
2003-03-19 14:11 ` frame->unwind->this_base() Daniel Jacobowitz
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=20030318173814.GA28471@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).