Most compilers emit the same thing for EH frame and for .debug_frame. If this
does indeed differ, then LLDB should parse both, but any such changes should
really do so in a way that prefers .debug_frame over .eh_frame since
.debug_frame should be complete unwind info even though it is just he sa
Yes sure.
On Wed, Nov 25, 2015 at 8:00 AM, wrote:
> lldb should be able to read both. Can you file a bug please?
> On Tue, Nov 24, 2015 at 02:50:20PM +0100, Ravitheja Addepally via lldb-dev
> wrote:
> > Hello,
> >While compiling with clang for i386, I notice that the CFI
> > information
lldb should be able to read both. Can you file a bug please?
On Tue, Nov 24, 2015 at 02:50:20PM +0100, Ravitheja Addepally via lldb-dev
wrote:
> Hello,
>While compiling with clang for i386, I notice that the CFI
> information is distributed between the .eh_frame section and the
> .debug_f
Hello,
While compiling with clang for i386, I notice that the CFI
information is distributed between the .eh_frame section and the
.debug_frame section, meaning for some functions the CFI info is present in
the .debug_frame section whereas for some it is present in the .eh_frame.
Now looking
