vscode: All breakpoints are unverified
- VSCode Version: 1.28
- Node Version: 10.12
- OS Version: Windows 10 1803
- Using Typescript: No
- Using Webpack: No
Launch configuration
{
"type": "node",
"request": "launch",
"name": "Launch Program",
"useWSL": true,
"program": "${workspaceFolder}\\index.js"
}
Steps to Reproduce:
- Add breakpoint which appears as a red filled circle
- Launch with above configuration
- Breakpoint turns to gray outline with hover of ‘Unverified breakpoint’
- Insert
debugger;
statement in code - File opens with subtitle ‘read-only core module’ in the titlebar
- Add breakpoint to this read-only file. This breakpoint works as expected
- Remove
debugger;
statement in editable source file - Add functioning breakpoints in the read-only file as required. They all work perfectly.
Line of Examination:
- Disabling sourceMaps in the launch configuration didn’t work
"localRoot": "${workspaceFolder}"
and"remoteRoot": "C:\\Users\\user\\folder"
did nothing. Code still opens in separate read-only file- Opening entire folder in Ubuntu and running launch as-is works perfectly. No issue with breakpoints at all.
I have been struggling with this issue since at least July 2018 without finding a working solution. I would be very grateful for help, since I have to go back to inserting console.log statements all over my code.
Does this issue occur when all extensions are disabled?: Yes
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 26 (13 by maintainers)
Commits related to this issue
- Fix debugging spaces in path with file: URIs Microsoft/vscode#61711 — committed to microsoft/vscode-chrome-debug-core by roblourens 6 years ago
- Bump node2 - #61711, #62354 — committed to microsoft/vscode by roblourens 6 years ago
Ok there seems to be a separate issue with WSL separate from the space issue, I’ll have to try it out.