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
Unable to debug with integrated terminal (WSL) #50445
Comments
Have you tried |
Yes, this changes what is executed in the terminal to:
So it attempts to run the node process using bash.exe, which shouldn't be necessary as it is doing that from within wsl to begin with, so just executing node should work. Either way as far as I can tell this isn't really relevant as the first statement Although the
So it seems It should make no difference to running bash.exe, but just in case my integrated terminal is running zsh via wsl.exe, with the following user setting:
Which works as the backslashes are escaped unlike in the statements VSCode attempts to execute. |
Ok, I guess it's assuming that your terminal is not already in WSL. @weinand do you know if this case should work? As a workaround, what if you remove useWSL and set |
This doesn't seem to be allowed: "Attribute 'cwd' is not absolute ('mnt/c/Code/debug'); consider adding '${workspaceFolder}/' as a prefix to make it absolute." And when I run it with any variation of |
I recently created a VS Code extension: WSL workspaceFolder, which may help. |
Hi @lfurzewaddock, your extension works on mine. Thanks a lot!! |
@adityawibisana What does your debug launch configuration look like in the end? |
|
@ltomes and @virgilwashere : first I need the extension, and it is working. Turn out that it is working without extension too. Last config:
On my case, most important part is the Do note that this one is |
I'd like to add to @adityawibisana's comment:
This makes the assumption that your
What's key is that your launch a node process with the |
@rozzzly : No, my package.json:
edited: I did |
That was 2 years ago. Unless you have a specific reason to use v7/the old protocol, using Also the port for Hopefully that clears up any confusion for a visitor from google in a year or two. 😉 |
@rozzzly : 💯 That was using node v5, anyway :) |
We just announced remote development with VS Code, check out the blog post for details https://code.visualstudio.com/blogs/2019/05/02/remote-development |
I'm having the same problem in the original post: cd: no such file or directory: c:Codedebug However, it works if I don't use the option I've installed the recent Remote WSL extension and it works in the WSL remote window, even with This is my launch configuration: |
@filetvignon the WSL extension is the solution to the problem, you cannot do it in a normal window by design. |
Please remove the |
Steps to Reproduce:
This then launches a new integrated terminal, and executes the following:
➜ cd c:\Code\debug && node --inspect-brk=30756
Which in my case is invalid due to the initial
cd c:\Code\debug
, as I am using wsl:cd: no such file or directory: c:Codedebug
I am aware of the previous issues involving this being closed as the problem was fixed, however this no longer seems to be the case.
Sample config:
The text was updated successfully, but these errors were encountered: