You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VS Code opening duplicate window with remote debugging and live reloading #3185
The default debug config in launch.json for Attach does not have the pathMappings. These are populated by the extension and passed to PTVSD.
At that point, the drive letter is in lower case, hence none of the path mappings work.
changed the title [-]VS Code opening duplicate window with remote debugging[/-][+]VS Code opening duplicate window with remote debugging and live reloading[/+]on Nov 5, 2018
I've not been able to repro this exact issue. The nearest issue I've encountered is that breakpoints are not respected when no localRoot or remoteRoot are supplied in launch.json.
I'm having this issue with Docker (didn't try outside of Docker, my workflow for now doesn't require it), easy repro. If I used c:\Users... as a root versus C:\users for example, it just works.
Activity
DonJayamanne commentedon Nov 2, 2018
Cause:
The default debug config in
launch.jsonforAttachdoes not have thepathMappings. These are populated by the extension and passed to PTVSD.At that point, the drive letter is in lower case, hence none of the path mappings work.
DonJayamanne commentedon Nov 2, 2018
Related to #2976
DonJayamanne commentedon Nov 2, 2018
Same as microsoft/ptvsd#973
[-]VS Code opening duplicate window with remote debugging[/-][+]VS Code opening duplicate window with remote debugging and live reloading[/+]d3r3kk commentedon Jan 10, 2019
I've not been able to repro this exact issue. The nearest issue I've encountered is that breakpoints are not respected when no
localRootorremoteRootare supplied inlaunch.json.DonJayamanne commentedon Jan 10, 2019
Remote debugging with lower case drive letter in path mappings.
20 remaining items
omartin2010 commentedon Feb 14, 2019
I'm having this issue with Docker (didn't try outside of Docker, my workflow for now doesn't require it), easy repro. If I used c:\Users... as a root versus C:\users for example, it just works.
DonJayamanne commentedon May 23, 2019
Closing as the upstream issue has been resolved.