Remote debug (PTVSD) path mapping

[omartin2010]

Issue Type: Bug

I simply launch my script on the target device :

sudo python3 -m ptvsd --host 0.0.0.0 --port 5678 --wait script.py

and when I launch the debugger on VSCode, I get this on the console of the remote device :

pydev debugger: warning: trying to add breakpoint to file that does not exist: /home/nvidia/c:/Users/omartin/OneDrive/Professionnel/Dev...

regarless of what the path mapping is (I've tried this :

"pathMappings": [ { "localRoot": "${workspaceFolder}", "remoteRoot": "/home/bob/" } ],

and it won't match go to /home/bob at all. Looks like something changed on the vscode side (python version, I've gone up to 2018.12 this morning and back to 2018.11 to test if that would be the cause (this all worked very well until this morning). This didn't solve the issue. Also vscode itself was updated but I'm not sure this has anything to do with this but clearly, something has changed...

Extension version: 2018.11.0
VS Code version: Code 1.30.0 (c6e592b2b5770e40a98cb9c2715a8ef89aec3d74, 2018-12-11T22:29:11.253Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)
GPU Status	2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: enabled video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled
Memory (System)	15.93GB (7.42GB free)
Process Argv
Screen Reader	no
VM	0%

[brettcannon]

Can you use VS Code's new feature to downgrade extensions and try older versions until you find one that works? Otherwise please make sure you are using the latest version of ptvsd on the remote machine.

[DonJayamanne]

• What version of PTVSD do you have installed on your remote environment?
• What is the remote root? is it /home/bob or /home/nvidia

[omartin2010]

I'm using ptvsd 4.2.0 on the remote machine, and tried vscode python extension 2018.12 and 2018.11 and both have the same issue.... but I was running the same yesterday (with 2018.11). The real root is actually /home/nvidia/BrickPi3/Software/Python/Examples and that's what I've got in the path mapping. But then I tried other settings as I've seen unexpected behavior... @brettcannon I guess when I installed 2018.11, it was using that feature? I've used the vsix option, uninstalled 2018.12 and then downloaded 2018.11 and installed it.

[cleverguy25]

I am facing this issue all of a sudden, and it worked yesterday. My work computer is down due to a power outage, but as soon as it is back up I will get the versions of everything.

[omartin2010]

btw I've tried 2018.12.1, 2018.12.0, 2018.11.0, 2018.10.01, 2018.10.0... same issue. And it was working last week. Since last week, VSCode's version also changed. Is there a part of the ptvsd "client" that isn't part of the python extension ?... is there anything you'd like me to share?

[omartin2010]

Ok, I just have found what I think is to be a workaround.
In the path mappings, I've had :
"pathMappings": [ { "localRoot": "${workspaceFolder}", "remoteRoot": "/home/bob/" }]
and I've replaced by:
`"pathMappings": [ { "localRoot": "c:\Users\.....\", "remoteRoot": "/home/bob/" } ],

where the c:\users is the actual path to the root of my project. Like if the workplaceFolder variable is broken, and/or not expanding properly anymore. Using the actual path works. Hope this helps identify the culprit.

[cleverguy25]

After I cleared my breakpoints and re-enabled them, I can confirm this works. I wonder if this is an issue with the breakpoints themselves, that they are mapping ${workspaceFolder} wrong

[DonJayamanne]

@cleverguy25

I can confirm this works.

What did you do to get this working?

[DonJayamanne]

@omartin2010

and I've replaced by:
`"pathMappings": [ { "localRoot": "c:\Users.....", "remoteRoot": "/home/bob/" } ],

Please could you change the drive letter to upper case C.
Also, how did you launch VS Code, did you launch from the terminal?
Please could you exit all instances of VS Code and re-open it and try it once again with ${workpaceFolder} instead of hard coding the paths as c:\....

[omartin2010]

I launched VS Code from the start menu. Upper case C makes it broken again, small 'c' makes it work. In fact, it's like this :
"pathMappings": [
{
//"localRoot": "${workspaceFolder}",
"localRoot": "c:\\Users\\omartin\\OneDrive\\Professionnel\\Dev\\RoboTeam\\",
"remoteRoot": "/src/repos/RoboTeam"
}

And that works... but not with upper case C... nor the ${workspaceFolder} variable.