[lldb-dev] eh_frame or debug_frame

[Francois Pichet]

On Fri, Oct 10, 2014 at 4:20 PM, Greg Clayton <gclayton at apple.com> wrote:

>
> > On Oct 10, 2014, at 1:05 PM, Philippe Lavoie <
> philippe.lavoie at octasic.com> wrote:
> >
> > Hi,
> >
> > I noticed that by default lldb does not read .debug_frame section to
> unwind frames but relies instead on .eh_frame .
> >
> > Is there a way to fallback to reading .debug_frame?
>
> Not currently. Most compilers (gcc _and_ clang) put the same old stuff in
> .debug_frame as they do in .eh_frame, so we haven't had to use .debug_frame
> over .eh_frame yet. What compiler are using that is putting different (more
> complete) info in .debug_frame vs .eh_frame?
>
>
> What about about C or C++ program compiled with -fno-exceptions?
They will fall back to the UnwindAssembly way even if the .debug_frame is
present right?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20141010/c2c14177/attachment.html>