| Issue |
162887
|
| Summary |
[lldb-dap] Make `"console": "integratedTerminal"` the default in the VSCode extension
|
| Labels |
lldb-dap
|
| Assignees |
|
| Reporter |
charles-zablit
|
When debugging `lldb` with `lldb-dap` in VSCode, with the following launch.json configuration, it's not possible to interact with the debuggee, as all the commands sent are passed to the debugger. This is solved by adding `"console": "integratedTerminal"` to the launch configuration.
```json5
{
"name": "lldb",
"type": "lldb-dap",
"request": "launch",
"program": "${workspaceFolder}/_build/Ninja-RelWithDebInfoAssert/lldb-macosx-arm64/bin/lldb",
"args": [
"/path/to/program"
],
//"console": "integratedTerminal"
},
```
`"console": "integratedTerminal"` is the default in CodeLLDB and I think it makes sense to have it that way as it allows the user to interact with their program by default.
## Default with `lldb-dap`
<img width="2654" height="812" alt="Image" src="" />
## Default with `CodeLLDB`
<img width="1199" height="401" alt="Image" src="" />
As an aside, I suspect CodeLLDB is using another mechanism than just `"console": "integratedTerminal"`, as the bar at the bottom of the `lldb` console does not appear when debugging with `CodeLLDB`, but it does with `lldb-dap`.
![]()
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
