On windows the script command does not produce any output though python is installed.
- Dominant language
- LLVM
- Stars
- 40.5k
- Forks
- 18.7k
- PR merge metrics
- PR metrics pending
Description
```
To get started with the debug console try "", "" or "help []"
For more information visit https://lldb.llvm.org/use/lldbdap.html#debug-console.
Running initCommands:
(lldb) settings set target.source-map C:\Users\jmfrank\source\repos\jmfrank63\Blitzkrieg C:\Users\jmfrank\source\repos\jmfrank63\Blitzkrieg
(lldb) settings set target.source-map C:\Users\jmfrank\scoop\apps\zig\0.16.0 C:\Users\jmfrank\scoop\apps\zig\current
(lldb) settings set target.inline-breakpoint-strategy always
Executable binary set to 'C:\Users\jmfrank\source\repos\jmfrank63\Blitzkrieg\zig-out\Game\x64\Debug\Game.exe' (x86_64-pc-windows-msvc).
Attached to process 14380.
version
lldb version 22.1.8 (https://github.com/llvm/llvm-project revision ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
clang revision ca7933e47d3a3451d81e72ac174dcb5aa28b59d1
llvm revision ca7933e47d3a3451d81e72ac174dcb5aa28b59d1
script import sys;print(sys.version);
script import sys;print(sys.version);sys.stdout.flush();
`script import sys;print(sys.version);sys.stdout.flush();
Process 14380 exited with status = 0 (0x00000000)
```
I have tried to set --repl-mode to auto and command but to no avail. I cannot so far confirm python311.dll is actually found for my installed 22.1.8 version of lldb-dap I can only confirm it for lldb.exe
I am currently investigating how to get python to work in the console.
Contributor guide
Research direction
Start with lldb-dap's --repl-mode handling and compare it with lldb.exe, checking whether python311.dll is loaded. Reproduce the Windows console commands shown, especially `script import sys;print(sys.version);sys.stdout.flush();`, and verify that the command produces Python version output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100