jmfrank63 wrote:
@charles-zablit
I have the results now, I have the new python manager installed python 3.14.6
first in path, and then the older python3.11 afterwards in path.
This results with the current code in python not found, though the extension
still works, as for my use case I do not need python. Berfore the extension
simply refused to start.
```
2026-08-06 15:04:59.933 [info] LLDB-DAP extension activating...
2026-08-06 15:04:59.933 [info] LLDB-DAP extension activated
2026-08-06 15:04:59.934 [info] Persisting lldb-dap logs to
c:\Users\jmfrank\AppData\Roaming\Code -
Insiders\logs\20260806T144609\window2\exthost\llvm-vs-code-extensions.lldb-dap
2026-08-06 15:04:59.937 [info] Resolving debug configuration for "Zig: Debug
Game.exe (x64, LLDB, No Build)"
2026-08-06 15:04:59.950 [info] lldb-dap path:
C:\Users\jmfrank\scoop\apps\llvm\current\bin\lldb-dap.exe
2026-08-06 15:04:59.950 [info] lldb-dap args:
2026-08-06 15:04:59.950 [info] cwd:
C:\Users\jmfrank\source\repos\jmfrank63\Blitzkrieg/zig-out/Game/x64/Debug
2026-08-06 15:04:59.950 [info] configured env:
{"LLDB_PYTHON_LIBRARY":"C:/Users/jmfrank/AppData/Local/Programs/Python/Python311/python311.dll"}
2026-08-06 15:05:00.364 [info] Skipped the Python runtime check: this lldb-dap
does not support "--check-python". Debugging will continue, but the extension
cannot verify your Python runtime before launch. If the debugger fails to
start, ensure the Python version LLDB was built against is installed and on
PATH.
Windows Python runtime search hint:
LLDB_PYTHON_LIBRARY=C:/Users/jmfrank/AppData/Local/Programs/Python/Python311/python311.dll;
PYTHONHOME=<unset>;
PATH(sample)=C:/Users/jmfrank/AppData/Local/Programs/Python/Python311;C:\WINDOWS\system32;C:\WINDOWS;...
(+30 more)
2026-08-06 15:05:01.164 [info] Resolved debug configuration:
{
"name": "Zig: Debug Game.exe (x64, LLDB, No Build)",
"type": "lldb-dap",
"request": "launch",
"program":
"C:\\Users\\jmfrank\\source\\repos\\jmfrank63\\Blitzkrieg/zig-out/Game/x64/Debug/Game.exe",
"initCommands": [
"settings set target.source-map
C:\\Users\\jmfrank\\source\\repos\\jmfrank63\\Blitzkrieg
C:\\Users\\jmfrank\\source\\repos\\jmfrank63\\Blitzkrieg",
"settings set target.source-map
C:\\Users\\jmfrank\\scoop\\apps\\zig\\0.16.0
C:\\Users\\jmfrank\\scoop\\apps\\zig\\current",
"settings set target.inline-breakpoint-strategy always"
],
"args": [],
"cwd":
"C:\\Users\\jmfrank\\source\\repos\\jmfrank63\\Blitzkrieg/zig-out/Game/x64/Debug",
"env": {},
"__configurationTarget": 6,
"debugAdapterHostname": "::1",
"debugAdapterPort": 52084
}
...
```
But any scripting will of course not work.
Additionally from powershell neither python nor python3
resolve to 311
```
❯ python311.exe
python311.exe: The term 'python311.exe' is not recognized as a name of a
cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path
is correct and try again.
~
❯ gcm python311
Get-Command: The term 'python311' is not recognized as a name of a cmdlet,
function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path
is correct and try again.
~
❯ gcm python3.exe
CommandType Name Version
Source
----------- ---- -------
------
Application python3.exe 0.0.0.0
C:\Users\jmfrank\AppData\Local\Microsoft\WindowsApps\python3.exe
~
❯ gcm python.exe
CommandType Name Version
Source
----------- ---- -------
------
Application python.exe 0.0.0.0
C:\Users\jmfrank\AppData\Local\Microsoft\WindowsApps\python.exe
```
The order is clearly correct:
```
$env:PATH
...
C:\Users\jmfrank\AppData\Local\Python\bin;C:\Users\jmfrank\AppData\Local\Programs\Python\Python311\;C:\Users\jmfrank\AppData\Local\Programs\Python\Python311\Scripts\;
```
The failure to resolve the version is a bug of either powershell or the python
manager.
`python --version` works.
Please let me know what your thoughts are.
https://github.com/llvm/llvm-project/pull/212989
_______________________________________________
lldb-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
