Apply this workaround only when the installed lldb.exe reports unable to find 'python311.dll'. It is specific to an LLDB build requiring Python 3.11; other builds may require a different runtime.
Provide Python 3.11 through uv and add its directory to the current PowerShell session's PATH:
uv python install 3.11
$lldbPythonDir = Split-Path (uv python find 3.11)
$env:PATH = "$lldbPythonDir;$env:PATH"Then run the already-built editor under LLDB. This example assumes the release output path; adjust it to the active build configuration:
lldb --batch -o "run --frames 3 --exit-after-load" -o "bt" -- build\windows\x64\release\editor.exeThe editor's launch arguments are handled in editor.cpp. Save debugger logs and crash artifacts under temp/.