-
Notifications
You must be signed in to change notification settings - Fork 68
Add support for remote source references #318
Comments
This wasn't a supported scenario for the old debugger in VS either, but it was always on the wish list. It certainly simplifies things quite a bit in exception debugging scenarios (which is pretty common for remote), since you don't need any local sources at all to attach and break on exception. We still need path mapping for breakpoints set in advance, so this can't fully replace that, but it's very useful even so. |
From what I can tell it works (provided the path mappings have been provided , i.e. #241 fixes that). |
What I meant is that you need a local source file that you can open and set a breakpoint inside, before you even attach (if you want to attach and hit a breakpoint, as opposed to attaching and breaking on exception). And I'd expect that in the scenario with mapping, it would just find that local file, instead of requesting the source remotely. |
Yes this would work, using what was implemented in #241
Yes |
Adds support for sourceReference
Scenarios:
breakpoint()
,ptvsd.wait_for_attach
orptvsd.break_into_debugger
oran exception
).I'd consider item 2 to be a great feature for release (I'm assuming this isn't already possible in PTVS, I know it isn't in VSC Python).
When does this come into play:
Only when remote debugging (
attach
) and if ptvsd is unable to map the server file to a client file (i.e. PTVSD is unable to map the file)Status
Items to consider/check:
@karthiknadig @int19h
Any thoughts/suggestions?
The text was updated successfully, but these errors were encountered: