[Lldb-commits] [PATCH] D62732: [RISCV] Add SystemV ABI
Tiancheng Zhang via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Tue Jul 26 10:07:22 PDT 2022
tzb99 added a comment.
In D62732#2790160 <https://reviews.llvm.org/D62732#2790160>, @sven wrote:
> In D62732#2790087 <https://reviews.llvm.org/D62732#2790087>, @luismarques wrote:
>
>> In D62732#2790028 <https://reviews.llvm.org/D62732#2790028>, @luismarques wrote:
>>
>>> That's surprising. I'll see if I can figure out what the issue might be. Thanks.
>>
>> Confirmed. Something must have broken since the last patch revision. I'll see if I can figure out / fix this soon.
>
> Hi @luismarques, @jade I have fixed the issue by install **libxml2-dev**, then recompile lldb and it works.
> The cause of this issue is that LLDB doesn't send qXfer command for register info which defined in qemu-gdb-stub xml if libxml2 is not installed.
> See ProcessGDBRemote.cpp::GetGDBServerRegisterInfo().
> Thank you for your help.
>
> // query the target of gdb-remote for extended target information returns
> // true on success (got register definitions), false on failure (did not).
> bool ProcessGDBRemote::GetGDBServerRegisterInfo(ArchSpec &arch_to_use) {
> // Make sure LLDB has an XML parser it can use first
> if (!XMLDocument::XMLEnabled())
> return false;
>
> But the unwind can not work on my machine, the issue is similar to which @jade reported
>
> (lldb) bt
> * thread #1, stop reason = breakpoint 1.1
> * frame #0: 0x0000000080000022 kern`fn3 at start.c:7:8
>
> Can you reproduce this problem? Or please show me how you fix the issue, thanks very much.
In D62732#2790160 <https://reviews.llvm.org/D62732#2790160>, @sven wrote:
> In D62732#2790087 <https://reviews.llvm.org/D62732#2790087>, @luismarques wrote:
>
>> In D62732#2790028 <https://reviews.llvm.org/D62732#2790028>, @luismarques wrote:
>>
>>> That's surprising. I'll see if I can figure out what the issue might be. Thanks.
>>
>> Confirmed. Something must have broken since the last patch revision. I'll see if I can figure out / fix this soon.
>
> Hi @luismarques, @jade I have fixed the issue by install **libxml2-dev**, then recompile lldb and it works.
> The cause of this issue is that LLDB doesn't send qXfer command for register info which defined in qemu-gdb-stub xml if libxml2 is not installed.
> See ProcessGDBRemote.cpp::GetGDBServerRegisterInfo().
> Thank you for your help.
>
> // query the target of gdb-remote for extended target information returns
> // true on success (got register definitions), false on failure (did not).
> bool ProcessGDBRemote::GetGDBServerRegisterInfo(ArchSpec &arch_to_use) {
> // Make sure LLDB has an XML parser it can use first
> if (!XMLDocument::XMLEnabled())
> return false;
>
> But the unwind can not work on my machine, the issue is similar to which @jade reported
>
> (lldb) bt
> * thread #1, stop reason = breakpoint 1.1
> * frame #0: 0x0000000080000022 kern`fn3 at start.c:7:8
>
> Can you reproduce this problem? Or please show me how you fix the issue, thanks very much.
Hi: I encountered the similar issue with the frame address showing all 1s. I tried to install libxml2-dev and wanted to recompile lldb. How did you recompile lldb? Do you cross compile or compile inside the qemu environment? If you do cross-compile, would you mind show the arguments of cmake? Thank you very much!
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D62732/new/
https://reviews.llvm.org/D62732
More information about the lldb-commits
mailing list