[llvm-bugs] [Bug 40569] New: lld-link puts non-canonical paths in debug information which confuses the VS debugger

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=40569

            Bug ID: 40569
           Summary: lld-link puts non-canonical paths in debug information
                    which confuses the VS debugger
           Product: lld
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: COFF
          Assignee: unassignedbugs at nondot.org
          Reporter: brucedawson at chromium.org
                CC: llvm-bugs at lists.llvm.org

When building Chrome binaries on Windows the debug information contains a
mixture of slashes, backslashes, and directory traversal characters, like this:

c:\src\chromium3\src>"c:\Program Files (x86)\Windows
Kits\10\Debuggers\x64\srcsrv\srctool.exe" -r out\default\base_unittests.exe.pdb
| find /i "run_all"
c:/src/chromium3/src/out/default\..\..\base\test\run_all_base_unittests.cc

windbg doesn't mind this (it finds the source files without difficulty) but VS
brings up the "Find Source" dialog. Once you find one source file it will
generally find all, and you can add source directory to your project files, but
none of this should be necessary.

We could file bugs against VS but it is probably better to see if
canonicalizing the paths in the debug information will make VS behave better.

I did my testing with no gn args (other than use_goma=true to accelerate
testing), building base_unittests. I tried setting msvc_use_absolute_paths =
true but that made no difference.

I tried building with use_lld=false and that avoided the problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20190202/e34586ce/attachment.html>