| Issue |
170461
|
| Summary |
Windows releases of LLDB should have libxml2 enabled if possible
|
| Labels |
lldb,
packaging,
platform:windows
|
| Assignees |
|
| Reporter |
DavidSpickett
|
A user reported in https://discourse.llvm.org/t/does-lldb-qemu-support-dumping-x64-control-registers-such-as-cr3/89031 that they weren't getting the expected registers from QEMU, and the cause is their LLDB not supporting target XML descriptions.
The release script does build libxml2 but it is not enabled for LLDB, are there known problems with using it? We at least know the user in that thread was able to rebuild with it enabled to solve their own issue.
This working out of the box would be great because a lot of debug servers now assume the client will rely on target XML.
https://github.com/llvm/llvm-project/blob/main/llvm/utils/release/build_llvm_release.bat
```
set common_lldb_flags=^
-DLLDB_RELOCATABLE_PYTHON=1 ^
-DLLDB_EMBED_PYTHON_HOME=OFF ^
-DLLDB_ENABLE_LIBXML2=OFF
```
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
