[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libunwind-devel] Libunwind support for CFI from .debug_frame in DWA

From: Andrew Cagney
Subject: Re: [Libunwind-devel] Libunwind support for CFI from .debug_frame in DWARF
Date: Wed, 07 Feb 2007 10:17:49 -0500
User-agent: Thunderbird (X11/20070102)


A standard "gcc -g" includes .debug_info but not .eh_frame (and often in a separate debug-info). By ignoring .eh_frame you're precluding any possibility of libunwind working effectively with that compiler. Can we revist this?


David Mosberger-Tang wrote:
Hi Corey,

On 2/6/07, Corey Ashford <address@hidden> wrote:

Are there any plans to add support to libunwind for the case when only
.debug_frame sections are present?

Can't speak for others, but I myself do not have plans for this.  As I
recall, I considered it briefly, but decided against it.  I think part
of it was that the info in .debug_frame isn't exactly the same as in
the .eh_frame sections.



I ask this knowing that the default switches for building Linux these
days includes -fexceptions, however many user apps will not have this
switch set.


As an aside, for the Frysk developers out there:

Is there some reliance on the -fasynchronous-unwind-tables switch being
used to compile the app-under-test besides getting libunwind to work?
In other words, are there other parts of Frysk that rely on .eh_frame

Thanks for your consideration,

- Corey

Corey Ashford
Software Engineer
IBM Linux Technology Center, Linux Toolchain
Beaverton, OR

Libunwind-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]