vscode: Unverified breakpoint error with build 1.25
I was debugging server side nodejs code using the latest production build (version 1.25) and it was refusing to respect breakpoints that I set. I had just upgraded from 1.24 and debugging sessions where working fine before upgrading.
Breakpoints seem to set ok (i.e. you see the red circle) when the code is not running, but as soon as you start running, the breakpoint turns transparent and the code will not break execution.
Mousing over the breakpoint displays “Unverified breakpoint” in the tooltip.
I am using Windows 10, WSL/ubuntu environment with useWSL:true
Here’s my launch.json
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"protocol": "inspector",
"request": "launch",
"name": "Run Elastc",
"program": "${workspaceFolder}/elastc.js",
"useWSL": true,
},
]
}

The fix is to revert back to 1.24 for now. You can get it from here: https://code.visualstudio.com/updates/v1_24
😦
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 5
- Comments: 21 (7 by maintainers)
Commits related to this issue
- Fix Microsoft/vscode#53785 - setBreakpoints override no longer needed, it will map remote paths twice — committed to microsoft/vscode-chrome-debug-core by roblourens 6 years ago
- Bump node2 for #53785 — committed to microsoft/vscode by roblourens 6 years ago
- Fix Microsoft/vscode#53785 - setBreakpoints override no longer needed, it will map remote paths twice — committed to microsoft/vscode-chrome-debug-core by roblourens 6 years ago
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
Thanks @fxlemire, same issue.
The fix will be in tomorrow’s insiders, I’d appreciate if anyone tries it out.
Great, thanks for verifying. Yes it will be in 1.25.1.
thanks @fxlemire I was going to get to it, been busy today…
@roblourens debugadapter.txt