-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging Rust with CodeLLDB opens WSL terminal instead of VS Code debug console #867
Comments
What is your shell for the integrated terminal? Try setting it to cmd if it isn't already. |
Where is the setting for this? EDIT: I set it to Powershell (F1 > Terminal: Select Default Profile) and VS Code still opens WSL. |
This problem is more about VSCode than it is about CodeLLDB, as the latter just requests that a command is executed in a terminal, the rest is done by VSCode, using its defaults, etc. |
That fixed it. Now the problem is that the window doesn't follow code execution, like how the Golang extension follows execution. EDIT: running it with {
"type": "lldb",
"request": "launch",
"name": "Debug Rust",
"cargo": {
"args": [
"run",
"--"
]
},
"args": [...],
} has it working now. |
|
Not sure what's up with your vscode configuration, but it should not be using WSL shell to launch commands requested by the debug adapter. The WSL shell obviously does not expect backslashes at a path separator, which causes the error you see. |
OS: Windows 11 Home 22H2 22621.1265
VSCode version: 1.75.1
CodeLLDB version: 1.8.1
Compiler: rustc 1.67.1
I'm trying to debug my Rust project with CodeLLDB and I want it to open the debugger in the built-in VS Code debug console. Instead, it opens a new WSL instance and tries to run the following in WSL:
My launch.json config is as follows:
Is there a way to get it to open the debug console?
Verbose log
The text was updated successfully, but these errors were encountered: