[LLDB] Fix loading modules outside container first that causes the failure of stack unwinding and step-in command · Pull Request !142 · OpenHarmony/third_party_llvm-project

## Issue

https://gitee.com/openharmony/third_party_llvm-project/issues/I6EC7I

## Description

As described in the issue [I6EC7I][1], in some cases, `lldb` is not able to unwind the stack so that the step command fails.

Details:

1. When the target platform is `remote-hos inner`, `PlatformHOS::GetFile` tries to load modules outside the container.

2. If two modules with the same path both exist inside and outside the container, and their content is different. The module outside the container will be pulled, but `lldb` client will never resolve it.

3. Since call frame information (CFI) is lost, unwinding of stack frames for functions in the unresolved modules is based on the frame pointer. If the frame pointer is used as a general-purpose register in these functions, stack unwinding will fail. In this case, stepping into a function call may stop at the trampoline (see an exmaple at [I6EC7I][1]).

Changes:

1. If the debuggee is inside the container, try to load modules inside the container.

[1]: https://gitee.com/openharmony/third_party_llvm-project/issues/I6EC7I

类型	指派人员	状态
审查	hhj 已审查通过 Pavel Kosov	已完成 (1/1人)
测试	openharmony_ci 已测试通过	已完成 (1/1人)

OpenHarmony/third_party_llvm-project .gitee-modal { width: 500px !important; }

搜索帮助

OpenHarmony/third_party_llvm-project