[lldb-dev] LLDB: Unwinding based on Assembly Instruction Profiling
Greg Clayton via lldb-dev
lldb-dev at lists.llvm.org
Wed Oct 14 13:36:19 PDT 2015
> On Oct 14, 2015, at 1:02 PM, Joerg Sonnenberger via lldb-dev <lldb-dev at lists.llvm.org> wrote:
>
> On Wed, Oct 14, 2015 at 11:42:06AM -0700, Greg Clayton via lldb-dev wrote:
>> EH frame can't be used to unwind when we are in the first frame because
>> it is only valid at call sites. It also can't be used in frames that
>> are asynchronously interrupted like signal handler frames.
>
> This is not necessarily true, GCC can build them like that. I don't
> think we have a flag for clang/LLVM to create full async unwind tables.
Most compilers don't generate stuff that is complete, and if it is complete, I am not aware of any markings on EH frame that states it is complete. So we really can't use it unless we know the info is complete. Was there ever an additional augmentation letter that was attached to the complete EH frame info?
More information about the lldb-dev
mailing list