https://bugs.llvm.org/show_bug.cgi?id=39503
Bug ID: 39503
Summary: Incorrect source paths generated for relative-path
source files
Product: lld
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: enhancement
Priority: P
Component: COFF
Assignee: unassignedb...@nondot.org
Reporter: brucedaw...@chromium.org
CC: llvm-bugs@lists.llvm.org
Starting probably in M71 the source path for invalid_parameter.cpp and probably
lots of other Microsoft source files changed. We can see this by retrieving
PDBs for M69 and M71 (chrome.dll.pdb and chrome.exe.pdb, but that difference is
irrelevant):
> cd etwpackage\bin
> retrievesymbols 8AFE809E8DA6300A4CD763DF535471FA 1 chrome.dll.pdb
> retrievesymbols 5FFDE2DF748D11544C4C44205044422E 1 chrome.exe.pdb
Then, use srctool to find the path to invalid_parameter.cpp:
> cd c:\Program Files (x86)\Windows Kits\10\Debuggers\x64\srcsrv
> srctool.exe -r
> c:\symbols\chrome.dll.pdb\8AFE809E8DA6300A4CD763DF535471FA1\chrome.dll.pdb |
> find "invalid_parameter.cpp"
minkernel\crts\ucrt\src\appcrt\misc\invalid_parameter.cpp
> srctool.exe -r
> c:\symbols\chrome.exe.pdb\5FFDE2DF748D11544C4C44205044422E1\chrome.exe.pdb |
> find "invalid_parameter.cpp"
C:\b\c\b\win64_clang\src\out\Release_x64\minkernel\crts\ucrt\src\appcrt\misc\invalid_parameter.cpp
This source file is supposed to have a relative path but now lld is giving it
an absolute path. This led to bucketing of unrelated crashes as
crbug.com/897677 (Google only) and eventually this was filed as a crash
processing bug as b/118710573. A workaround is being created but the root cause
should be addressed.
This is presumably an obvious (in hindsight) consequence of the changes to make
reproducible builds.
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
