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

Cannot debug node v6.3.0 when files resides on a subst drive #8958

Closed
Loghorn opened this issue Jul 8, 2016 · 1 comment
Closed

Cannot debug node v6.3.0 when files resides on a subst drive #8958

Loghorn opened this issue Jul 8, 2016 · 1 comment
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@Loghorn
Copy link

Loghorn commented Jul 8, 2016

  • VSCode Version: Code - Insiders 1.4.0-insider (4b84f6d, 2016-07-08T07:45:28.445Z)
  • OS Version: Windows_NT ia32 10.0.14383

Steps to Reproduce:

  1. create a new folder (e.g. C:\test)
  2. run subst X: C:\test
  3. open the root of drive X: in VSCode
  4. create a new javascript file with some code (a simple console.log(__dirname) will do)
  5. configure VSCode to start the file you just created
  6. set a breakpoint in the file
  7. start debugging
  8. PROBLEM: the breakpoint is never hit.

This is related to nodejs issue #7294

@joshgav
Copy link

joshgav commented Jul 8, 2016

See nodejs/node#7559 for work on fixes.

/cc @bzoz

@mjbvz mjbvz added the javascript JavaScript support issues label Nov 11, 2016
@weinand weinand added bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed javascript JavaScript support issues labels Apr 6, 2017
@weinand weinand closed this as completed Apr 6, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
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 upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

4 participants