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.

Sign up for GitHub

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

Jump to bottom

"Path must be string. Received null" error when attempting to start debugger #3625

Closed
jumpinjackie opened this issue Mar 2, 2016 · 6 comments
Closed

"Path must be string. Received null" error when attempting to start debugger #3625

jumpinjackie opened this issue Mar 2, 2016 · 6 comments
Assignees
@weinand
Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority
Milestone
Feb 2016

Comments

@jumpinjackie
Copy link

Using VSCode 0.10.10-insider on Windows 7

I can no longer debug my JavaScript in this build. It just throws this error

capture

Falling back to the 0.10.8 release on the "stable" channel, I can debug this project again. I could also debug this project with the previous insiders build.

To reproduce:

  1. Clone my repo https://github.com/jumpinjackie/jsdoc-typescript-plugin
  2. npm install
  3. npm run-script tsc
  4. Open this clone dir in VSCode 0.10.10-insider
  5. Start debugging with the provided launch.json

As an aside, it would be nice for such errors to present an option to show the stack trace as well, because I have no clue where to even look to determine the cause of this problem.
@isidorn isidorn self-assigned this Mar 2, 2016
@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Mar 2, 2016
@isidorn isidorn added this to the March 2016 milestone Mar 2, 2016
@weinand weinand assigned weinand and unassigned isidorn Mar 3, 2016
@weinand weinand modified the milestones: Feb 2016, March 2016 Mar 3, 2016
weinand added a commit to microsoft/vscode-node-debug that referenced this issue Mar 3, 2016
@weinand
check for 'outDir' being null or undefined; fixes microsoft/vscode#3625
ff25cd4
@weinand
Copy link
Contributor

weinand commented Mar 3, 2016

@jumpinjackie sorry for this regression. The workaround is to set outDir to the path where the source maps exist, e.g. for the project from above ${workspaceRoot}/plugins.

You can find the stacktrace for the error in the dev tools console of VS Code.

@weinand weinand added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority stable-candiate labels Mar 3, 2016
@weinand weinand closed this as completed Mar 3, 2016
weinand added a commit that referenced this issue Mar 3, 2016
@weinand
check for 'outDir' being null or undefined; fixes #3625
c259068
weinand added a commit to microsoft/vscode-node-debug that referenced this issue Mar 3, 2016
@weinand
check for 'outDir' being null or undefined; fixes microsoft/vscode#3625
763bf27
@weinand weinand mentioned this issue Mar 4, 2016
Closed
@saravmajestic
Copy link

I am getting the same error when trying to install "Cordova tools".
Steps:

  • Installed VSCode Version 0.10.9 (0.10.9)
  • installed cordova extension from extensions gallery
  • selected Cordova from debug configuration
  • clicked 'Run Android on emulator'
    Got the error as above.

I tried to set sourceMaps as false and "outDir": "${workspaceRoot}" , but still getting same error.

I dont know which sourcemaps I have to specify as mentioned in the workaround. I am using Mac 10.10.5

@weinand
Copy link
Contributor

weinand commented Mar 6, 2016

@saravmajestic please report your problem against the Cordova tools.

@saravmajestic
Copy link

screen shot 2016-03-06 at 5 46 28 pm

@weinand attached the screenshot. I will report the same in Cordova tools as well. Thanks a lot!

@saravmajestic saravmajestic mentioned this issue Mar 6, 2016
Closed
@weinand
Copy link
Contributor

weinand commented Mar 6, 2016

@saravmajestic thanks! Yes, the error message shows that this is not a VS Code problem but a problem in the Cordova extension.

@egamma
Copy link
Member

egamma commented Mar 7, 2016

@saravmajestic this is the repository of the Cordova extension https://github.com/Microsoft/vscode-cordova

@jamietre jamietre mentioned this issue Oct 7, 2016
Closed
@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.
Assignees

@weinand weinand

Labels
bug Issue identified by VS Code Team member as probable bug debug Debug viewlet, configurations, breakpoints, adapter issues important Issue identified as high-priority
Projects
None yet
Milestone
Feb 2016
Development

No branches or pull requests
5 participants
@egamma @jumpinjackie @saravmajestic @weinand @isidorn