-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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.
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
Unbound breakpoint #106795
Comments
(Experimental duplicate detection) |
In the log file you included, the only three scripts the browser loaded were:
It doesn't look like your own code is loaded in the browser. Therefore we cannot set the breakpoint and mark it with an empty circle. |
Issue Type: Bug I have re-run again, trying to set a breakpoint in my typescript code. I can see the code and set a breakpoint using chrome's internal debugger but can not do so from visual studio code. VS Code version: Code - Insiders 1.50.0-insider (e13875b, 2020-09-15T05:35:57.362Z) System Info
Extensions (6)
|
I notice in your logs that you're opening a new window, 22 seconds into debugging. Are you trying to debug your the sources in there? You'll need update your urlFilter to include that if, so, which you can do by setting |
Adding 'urlFilter' solved the problem. Documentation about this option was not clear on this point. Nowhere that I could see did it say anything about what happens if multiple windows are opened. I have been used to the PHP debugger which does not use such an option. I had assumed wrongly that the javascript debugger worked in a similar manner. Thank you for pointing this out. Everything is now working. |
I think that defaulting the urlFilter is |
Does that mean that it will auto attach to new tabs or windows? |
That was my expectation when I used the javascript debugger. |
I see it. Cool, it's probably fine. It could be annoying if someone is using the same browser for some other tabs that they don't want to debug, especially if those pages throw exceptions or something. But I would think that most likely they'd be using another browser/another chrome profile for that. |
It might make sense to actually name it "auto attach" or think about how it relates to node auto attach. Also as a launch config option vs user setting. |
Well, it's kind a matrix of both. As a user, the preference of whether or not to attach to other tabs in the debug target is a personal one. But for an app, I could know that I want to debug all of these specific urls. Which is additional configuration to conceptualize. The exception case is annoying, but it will also be kind of apparent what happened in most cases. Probably... I think a default of I'll toggle it on Insiders and see if we get any complaints about it. |
Same bug here: Start to happen on Version: 1.49.0 |
If the solution above doesn't work for you, you likely have a different issue and should open a bug here 🙂 https://github.com/microsoft/vscode-js-debug/issues |
We have written the needed data into your clipboard because it was too large to send. Please paste.
Issue Type: Bug
I have been setting a breakpoint on some typescript code and launch the chrome debugger. Once chrome has loaded the breakpoint changes from solid red to grey open circle and message Unbound Breakpoint.
I have searched GitHub but there does not seem to be a fix for this issue.
VS Code version: Code - Insiders 1.50.0-insider (e13875b, 2020-09-15T05:35:57.362Z)
OS version: Windows_NT x64 10.0.19041
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Extensions (5)
launch.json
vscode-debugadapter-0.json.gz
The text was updated successfully, but these errors were encountered: