codelldb
codelldb copied to clipboard
vadimcn
PDB with UNC source paths don't resolve correctly on Windows.
OS: Windows 11 VSCode version: Version: 1.70.0-insider, Commit: 12b08be500f8a307f30e92cbc3ee39ba CodeLLDB version: 1.7.3 Compiler: rustc 1.62.1 Debuggee: shared library built in rust
For reason not known to me rust build seem to be product pdb that has unc source path, i.e.
\\?\C:\Users\matej\Projects\super_native_extensions\super_native_extensions
For some reason this is not handled correctly by vscode, the disassembly header shows
Source location: \?\C:\Users\matej\Projects\super_native_extensions\super_native_extensions\
Not entirely sure if this is bug with vscode-lldb or vscode itself.
Note that other pdb files (that use simply absolute path, i.e. C:\) resolve correctly.
Can you please explain what exactly was meant by "don't resolve correctly"? What is broken?
When source location in pdb starts with \\?\C:\Users\... vscode will try opening the source file in \?\C:\Users\, which is not a valid UNC path (note missing slash at the beginning).
I can't reproduce this, for me rustc seems to output normal paths.
Regardless, I doubt VSCode will be able to handle UNC. Just try typing a UNC path in File/Open dialog: the dialog itself seems to handle it okay, however, once I hit enter, VSCode says the file name is invalid.