From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: Mark Kettenis <kettenis@chello.nl>, gdb@sources.redhat.com
Subject: Re: [RFC] DWARF CFI: what to do with .eh_frame sections?
Date: Fri, 09 May 2003 22:27:00 -0000 [thread overview]
Message-ID: <20030509222736.GA30307@nevyn.them.org> (raw)
In-Reply-To: <3EBC2482.2010203@redhat.com>
On Fri, May 09, 2003 at 05:58:26PM -0400, Andrew Cagney wrote:
> >On Fri, May 09, 2003 at 10:14:34PM +0200, Mark Kettenis wrote:
> >
> >>It's clear that we want to support unwinding using info in .eh_frame
> >>sections in addition to .debug_frame sections. I'm inclined to make
> >>to make dwarf-frame.c provide two frame unwinders: one that uses
> >>.debug_frame info, and one that uses .eh_frame info. That way it will
> >>be possible to let the target determine if .dwarf_frame will be
> >>preferred over .eh_frame or not.
> >>
> >>Thoughts?
> >
> >
> >That seems reasonable. I'd probably create a single function to
> >register both unwinders, and call it from each target, though;
> >since there's no reason I can think of to prefer one over the other
> >modula unknown GDB bugs.
>
> Think of it as a two tiered effect, you know with ... (sorry).
>
> If I understand the cfi stuff correctly, it can be broken down into:
>
> - the cfi engine
> - the cfi byte stream source
>
> (kind of like dwarf2expr) The latter can be debug info, .eh_frame, or
> even (as long a go proposed) hand written code.
Ah yes, I'd forgotten about this. It's becoming less important but it
would still be useful.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-05-09 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 20:14 Mark Kettenis
2003-05-09 20:20 ` Daniel Jacobowitz
2003-05-09 21:58 ` Andrew Cagney
2003-05-09 22:27 ` Daniel Jacobowitz [this message]
2003-05-09 23:59 ` 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=20030509222736.GA30307@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@redhat.com \
--cc=gdb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).