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

Remote WSL breaks the javascript debugger auto-attach if node isn't the topmost process #1212

Closed
vvilhonen opened this issue Feb 16, 2022 · 4 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@vvilhonen
Copy link

vvilhonen commented Feb 16, 2022

Wrapping node in another process makes the javascript debugger to search sourcemaps from the host filesystem instead of from inside WSL.

Running node topmost:

works

Wrapping node with another node:

doesnt work

  • Remote OS Version: Ubuntu 20.04.3 LTS
  • Remote Extension/Connection Type: WSL
  • Logs:
Version: 1.65.0-insider (user setup)
Commit: 52e65499654de7525e30df3a8228b69320796bf5
Date: 2022-02-16T05:16:18.653Z
Electron: 16.0.9
Chromium: 96.0.4664.174
Node.js: 16.9.1
V8: 9.6.180.23-electron.0
OS: Windows_NT x64 10.0.19043

Steps to Reproduce:

  1. Clone https://github.com/vvilhonen/vscode-remote-debugger-wsl-sourcemap-problem
  2. Enable vscode debugger auto-attach
  3. Set breakpoint on any line on src/yo.ts
  4. Open integrated terminal
yarn
yarn compile

# Works
node dist/yo.js

# Doesn't work
node wrapped-node.js

# Doesn't work
yarn node dist/yo.js
@github-actions github-actions bot added the wsl label Feb 16, 2022
@bamurtaugh
Copy link
Member

@connor4312 any thoughts?

@connor4312 connor4312 added bug Issue identified by VS Code Team member as probable bug and removed wsl labels Feb 23, 2022
@connor4312 connor4312 self-assigned this Feb 23, 2022
@connor4312 connor4312 transferred this issue from microsoft/vscode-remote-release Feb 23, 2022
@connor4312 connor4312 added this to the March 2022 milestone Feb 23, 2022
@connor4312
Copy link
Member

Thanks for the nice repro!

@vvilhonen
Copy link
Author

Thanks!

@rchiodo
Copy link

rchiodo commented Mar 25, 2022

/verified

@rchiodo rchiodo added the verified Verification succeeded label Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

4 participants