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. So at frame zero, we typically just fall back to the default unwind plan for the current architecture which is usually follow the frame pointer for most systems.
> On Oct 14, 2015, at 1:49 AM, Abhishek Aggarwal via lldb-dev > <lldb-dev@lists.llvm.org> wrote: > > Hi > > As far as I know, if the unwinding based on Assembly Instruction > Profiling fails in LLDB then either EH frame unwinding or some other > mechanism comes into picture to unwind properly. Am I right? > > In this case, should LLDB change the unwinder plan from Assembly > Instruction Profiling to EH Frame based unwinding so that in future > the unwinding is always done with the new unwind plan rather than > first checking the assembly based unwind plan and then falling back to > EH Frame based unwind plan? > > > Thanks > _______________________________________________ > lldb-dev mailing list > lldb-dev@lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev _______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
