Debugger issues related to path mappings and case sensitive paths
See original GitHub issue-
If drive letter is in lower case, then path mappings will not work
-
Note: Its possible drive letter can be in lower case (e.g. user set path in shell using a lower case drive letter, e.g.
cd c:/x....
(at this point, all paths have lower casec
). -
Debugging opens new all-lowercase file #5049 (PTVSD)
-
Debugger does not work with google drives designated as g: or any drive letter #4658 (VSCode)
-
Remote debugging fails due to incorrect path mappings #5075 (PTVSD, Path Mapping)
-
Remote debugging failed #5094 (PTVSD, Path Mapping)
-
Duplicate file tab during debugging on Windows #4166
-
Multi process debugging with launch does not work due to path mappings
- Solution https://github.com/Microsoft/vscode-python/issues/3568 April Sprint
-
VS Code opening duplicate window with remote debugging and live reloading #3185 (VS Code https://github.com/Microsoft/vscode/issues/67523)
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:8 (2 by maintainers)
Top GitHub Comments
FYI, this is a blocker (on Windows or other case-insensitive filesystems) for path mappings that use
${workspaceFolder}
. Because${workspaceFolder}
is normalized to all-lower-case, it always results in a case-mismatch. If I replace${workspaceFolder}
with the hard-coded (case-sensitive) absolute path, it works. But this is not portable.With a breakpoint in
foo/bar/main.py
, I receive this error message:Where the path should be
/var/task/main.py
.Closing this as stale. Please create separate bugs if this are still occurring.