-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issues
Milestone
Description
- 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
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesDebug viewlet, configurations, breakpoints, adapter issues