================
@@ -2530,9 +2530,6 @@ StructuredData::DictionarySP
Debugger::GetBuildConfiguration() {
AddBoolConfigEntry(
*config_up, "lua", LLDB_ENABLE_LUA,
"A boolean value that indicates if lua support is enabled in LLDB");
- AddBoolConfigEntry(*config_up, "fbsdvmcore", LLDB_ENABLE_FBSDVMCORE,
- "A boolean value that indicates if fbsdvmcore support is "
- "enabled in LLDB");
----------------
DavidSpickett wrote:
Also stuff like this shows up in this command we recommend for troubleshooting:
```
(lldb) version -v
lldb version 23.0.0git (https://github.com/llvm/llvm-project.git revision
1466e59d32e68dacde914a175a2dd3876bb38c24)
clang revision 1466e59d32e68dacde914a175a2dd3876bb38c24
llvm revision 1466e59d32e68dacde914a175a2dd3876bb38c24
editline_wchar: yes
lzma: yes
curses: yes
editline: yes
fbsdvmcore: yes
xml: yes
lua: no
zlib: yes
python: yes
curl: no
targets: [AArch64, AMDGPU, ARM, AVR, BPF, Hexagon, Lanai, LoongArch, Mips,
MSP430, NVPTX, PowerPC, RISC
V, Sparc, SPIRV, SystemZ, VE, WebAssembly, X86, XCore]
```
So it's misleading to leave this config entry in because it implies that
fbsdvmcore *could* have been enabled, when in fact now, there's literally no
way to enable it.
https://github.com/llvm/llvm-project/pull/183418
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
