Hi Alexander, sorry for the delay in replying.
The attached unwind log shows that lldb is using the architectural default
unwind plan for this target. You can see where this unwind plan in constructed
at
ABISysV_mips::CreateDefaultUnwindPlan
it says to find the caller's pc value at *($r29),
https://bugs.llvm.org/show_bug.cgi?id=44059
Djordje Todorovic changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.llvm.org/show_bug.cgi?id=44690
Gabor Greif changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED
On 27/01/2020 19:43, Alexander Zhang via lldb-dev wrote:
> Hi,
>
> Thanks for pointing me towards stack unwinding. I don't have debug
> information much of the time, so I'm depending on the architecture rules
> for backtracing. A look at the mips ABI plugin shows it uses dwarf
> register numbers t
