This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 119
Breakpoints sometimes don't get hit #536
Comments
Would be helpful if you can get a log. You can set |
I haven't see this same behavior in a while, but related behavior is setting BP that seemingly get set, but are apparently set in the completely wrong sourcemap location. Here is my log: vscode-node-debug2.zip
In there you can see that it mapped from one of my other extensions to gitlens:
|
Yeah, we don't have the concept of multiple "projects" with sourcemaps resolved independently, so this can happen, especially with webpack paths that lose context. But connor used a different strategy in vscode-pwa and it should actually be fixed there though! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was doing a lot of debugging the other night and I kept running into issue where I'd set a breakpoint (and it would show in the UI as red), but the debugger wouldn't stop at that point. And if I reset (clear/add) the BP, then it would get hit. This happened quite a few times, but unfortunately I don't have any logs or anything to provide here. I was debugging both vscode itself and an extension and I saw the behavior in both.
The text was updated successfully, but these errors were encountered: