[lldb, Windows 11] LLDB executable crashes on every invocation

[TahaAhmedRasheed]

Attempting to run lldb will always cause it to crash immediately:

Calling lldb from git bash reveals more info:

C:/Program Files/LLVM/bin/lldb.exe: error while loading shared libraries: ?: cannot open shared object file: No such file or directory

Other applications from the llvm suite like clang, clang-format, clangd work without issues on this system.
I got my installation of LLVM from: https://github.com/llvm/llvm-project/releases/tag/llvmorg-15.0.5

LLVM info: 15.0.5
OS: Windows 11

[llvmbot]

@llvm/issue-subscribers-lldb

[TahaAhmedRasheed]

start lldb further reveals that LLDB is missing python310.dll, which should not actually be an issue since I have python 3.11 installed and on my path:

[TahaAhmedRasheed]

Found a workaround: Copy everything from inside the "python 3.10 embeddable package" folder into the llvm/folder. However, this is a pretty shoddy solution and llvm should just work with an up-to-date python version out of the box.

[jimingham]

Unlike most of the rest of llvm, lldb uses the Python C API's extensively. And though Python has a subset of the API that's supposed to be binary stable, lldb can't implement all the interactions with Python it needs to do using only that part of the Python C API's. Someone tried a while back, but didn't get very far. I haven't seen Python make specific claims for the resilience of the non-binary-stable parts of the API, but our experience is that using any other version of Python than the one we built against is very fragile. We've seen cases where even using a differently build Python from the same sources has caused Python crashes in the lldb module. So we try to make sure lldb is using just the Python we built against. I don't work on the Windows side of things, so I don't know how packaging is supposed to work there. We should always provide a Python library that we know is going to work, however, rather than hoping we get lucky with whatever was installed on the system. But I don't know how that's implemented. Jim

…

On Dec 14, 2022, at 12:15 PM, TahaAhmedRasheed ***@***.***> wrote: Found a workaround: Copy everything from inside the "python 3.10 embeddable package" folder into the llvm/folder. However, this is a pretty shoddy solution and llvm should just work with an up-to-date python version out of the box. — Reply to this email directly, view it on GitHub <#59524 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADUPVWZNLBZOZH35IPWIWHDWNITHPANCNFSM6AAAAAAS63DYKY>. You are receiving this because you are on a team that was mentioned.

[Drllap]

Ran into issue with:
LLVM v16.0.1
Windows 10

Installed using chocolatey

[Unkorunk]

Ran into issue with:
LLVM v16.0.0 and v16.0.4
Windows 11 Home

Installed using installer from Release tab

[SanderVocke]

I seem to have ran into this on Github Actions (windows-2022 runner) with Chocolatey-installed LLVM.