Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Conversation

@bzoz
Copy link
Contributor

@bzoz bzoz commented Sep 20, 2017

Continued from #126. Refactored like microsoft/vscode-node-debug#158., to add WSL support for inspector protocol.

Add new "useWSL" launch attribute. When used, Bash on Windows will be used to launch runtimeExecutable. Source files directory mapping will also be automatically added.

/cc @weinand

Add new "useWSL" launch attribute. When used, Bash on Windows will be
used to launch runtimeExecutable. Source files directory mapping will
also be automatically added.
@alanosman
Copy link

When will this make it's way into the insiders build?

@roblourens roblourens added this to the October 2017 milestone Sep 29, 2017
@yodurr
Copy link

yodurr commented Oct 4, 2017

Are you asking when with the WSL support for this arrive on Windows 10 insiders? If yes, you can use the current retail Windows 10 (creators update) for this or any insiders release since. No recent WSL work was required to support this.

@alanosman
Copy link

@yodurr I am asking "when can we debug a node app running on WSL from Visual Code". i.e. set a breakpoint in your node code, press F5 and start debugging, but with the process launching inside bash, Currently, you can only attach to a bash node process through a port. It would be nice to launch and go right into debugging.

@Alkasai
Copy link

Alkasai commented Oct 4, 2017

@yodurr I think @alanosman was referring to the VSCode Insiders.

@roblourens
Copy link
Member

This is in node-debug ("legacy") but not node-debug2 ("inspector"). @weinand does this PR match what's in node-debug now?

@bzoz
Copy link
Contributor Author

bzoz commented Oct 4, 2017

@roblourens yes, this reimplementation of the method that was added to vscode-node-debug

@yodurr
Copy link

yodurr commented Oct 4, 2017

Thanks for clarifying. Agree @alanosman the scenario you describe is what we're excited about seeing supported. This PR makes it happen.

@alanosman
Copy link

@yodurr so, just so I am clear, this is not in the insiders build yet, right?

Copy link
Member

@roblourens roblourens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also the spelling of the new file (Liunux)


const port = args.port || utils.random(3000, 50000);

if (args.useWSL && !wsl.subsystemLinuxPresent) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

subsystemLinuxPresent is a function

@bzoz
Copy link
Contributor Author

bzoz commented Oct 9, 2017

Updated

@roblourens
Copy link
Member

Thanks! I'll publish this and pull it into the vscode build so it's available in the next Insiders build. Then it will be in stable 1.18, the first week in November.

@roblourens roblourens merged commit 366dc7a into microsoft:master Oct 9, 2017
@roblourens
Copy link
Member

FYI @weinand I took this and found some tweaks in node-debug, and copied your fix from microsoft/vscode-node-debug@3a0f1a8#diff-2a53bfce93d1a0ef575c1c6581a6cb1b. LMK if you can think of anything else I need to change.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants