Skip to content
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

version 1.25.0 can not debug in WSL #53674

Closed
LeoYoung opened this issue Jul 6, 2018 · 9 comments
Closed

version 1.25.0 can not debug in WSL #53674

LeoYoung opened this issue Jul 6, 2018 · 9 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)

Comments

@LeoYoung
Copy link

LeoYoung commented Jul 6, 2018

Issue Type: Bug

When I update VS code to version 1.25.0
I found that the breakpoint not hit when debugging (I'm using WSL)
I have set "useWSL": true in launch.json and it works well in version 1.24.1

VS Code version: Code 1.25.0 (0f080e5, 2018-07-05T13:11:58.697Z)
OS version: Windows_NT x64 10.0.17134

System Info
Item Value
CPUs Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (4 x 3192)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: disabled_software
video_decode: enabled
video_encode: enabled
vpx_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 7.95GB (3.29GB free)
Process Argv C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader no
VM 50%
Extensions (16)
Extension Author (truncated) Version
vscode-eslint dba 1.4.12
javascript-ejs-support Dig 0.3.2
gitlens eam 8.4.1
EditorConfig Edi 0.12.4
php-debug fel 1.12.3
beautify Hoo 1.3.2
docthis joe 0.7.1
vscode-language-pack-zh-hans MS- 1.25.3
cpptools ms- 0.17.6
csharp ms- 1.15.2
debugger-for-chrome msj 4.7.0
vetur oct 0.12.5
material-icon-theme PKi 3.5.1
ayu tea 0.14.0
vscode-todo-highlight way 0.5.12
markdown-all-in-one yzh 1.5.1
@vscodebot vscodebot bot added the new release label Jul 6, 2018
@weinand weinand added the debug Debug viewlet, configurations, breakpoints, adapter issues label Jul 6, 2018
@weinand
Copy link
Contributor

weinand commented Jul 6, 2018

@LeoYoung what version of node.js are you using in WSL?
You can find out by running this in Windows:

wsl node --version

@weinand weinand added the info-needed Issue requires more information from poster label Jul 6, 2018
@fxlemire
Copy link

fxlemire commented Jul 6, 2018

I have the same problem, I have version 8.9.4 in WSL.

The following config used to work before upgrading to 1.25.0 (i.e. 1.24.1):

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "launch",
            "name": "Mocha Current File",
            "program": "${workspaceFolder}/node_modules/mocha/bin/_mocha",
            "args": [
                "--timeout",
                "999999",
                "--colors",
                "${relativeFile}"
            ],
            "localRoot": "${workspaceRoot}",
            "remoteRoot": "/mnt/c/Users/<USERNAME>/Documents/smooch",
            "protocol": "inspector",
            "useWSL": true
        }
    ]
}

@LeoYoung
Copy link
Author

LeoYoung commented Jul 7, 2018

@weinand thank you for reply
my node version is 8.11.2 and npm version is 6.1.0

BTW
I also have a laptop which has a very same environment to my desktop
like same OS version, same WSL version, also same node version
but this device is still in 1.24.1 yet and works well
Is there any way to dump the information of debugging ?
Maybe it can help us to find the problem

@weinand
Copy link
Contributor

weinand commented Jul 9, 2018

Most likely this issue is a duplicate of #53785 for which there will be a fix in tomorrow's Insider build.

It would be great if you could verify that this fixes the WSL issue as well.

@weinand weinand added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Jul 9, 2018
@LeoYoung
Copy link
Author

@weinand
I have tried the new Insider build (Version 1.26.0)
It seems that this bug has been fixed, THANKS👍

@weinand
Copy link
Contributor

weinand commented Jul 10, 2018

@LeoYoung great, thanks a lot for verifying this.

@fxlemire
Copy link

I confirm, also works on my end! 👍

@weinand
Copy link
Contributor

weinand commented Jul 10, 2018

duplicate of #53785

@weinand weinand added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 10, 2018
@vscodebot
Copy link

vscodebot bot commented Jul 10, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Jul 10, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues *duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

3 participants