New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 754277 link

Starred by 2 users
Status: Fixed
Owner:
█ zturner@chromium.org
Last visit > 30 days ago
Closed: Nov 2017
Cc:
r...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug

Blocking:
issue 82385



Sign in to add a comment

CrWinClngLLDdbg bot red

Project Member Reported by thakis@chromium.org, Aug 10 2017 
last good: llvm 310407 -- https://build.chromium.org/p/chromium.fyi/builders/CrWinClngLLDdbg/builds/6523
first bad:  llvm 310442 -- https://build.chromium.org/p/chromium.fyi/builders/CrWinClngLLDdbg/builds/6524

[42320/54401] LINK(DLL) blink_core.dll blink_core.dll.lib blink_core.dll.pdb
FAILED: blink_core.dll blink_core.dll.lib blink_core.dll.pdb 
C:/b/depot_tools/win_tools-2_7_6_bin/python/bin/python.exe ../../build/toolchain/win/tool_wrapper.py link-wrapper environment.x86 False ../../third_party/llvm-build/Release+Asserts/bin/lld-link.exe /nologo /IMPLIB:./blink_core.dll.lib /DLL /OUT:./blink_core.dll /PDB:./blink_core.dll.pdb @./blink_core.dll.rsp
Failure value returned from cantFail wrapped call
UNREACHABLE executed at C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm\include\llvm/Support/Error.h:1055!
Wrote crash dump file "c:\b\rr\tmppcqa6_\t\lld-link.exe-37f6c2.dmp"
#0 0x000000013f211235 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x81235)
#1 0x0000000140cc5ed5 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1b35ed5)
#2 0x0000000140cc58b8 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1b358b8)
#3 0x000000013f21141e (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x8141e)
#4 0x000000013fff0a57 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xe60a57)
#5 0x000000013f3faaf1 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x26aaf1)
#6 0x000000013f3f9eaa (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x269eaa)
#7 0x000000013f2971df (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1071df)
#8 0x000000013f284d22 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xf4d22)
#9 0x000000013f2851cc (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xf51cc)
#10 0x000000013f264c16 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xd4c16)
#11 0x000000013f264df4 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0xd4df4)
#12 0x000000013f1ff822 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x6f822)
#13 0x0000000140c9d199 (C:\b\c\builder\CrWinClngLLDdbg\src\third_party\llvm-build\Release+Asserts\bin\lld-link.exe+0x1b0d199)
#14 0x00000000779d59cd (C:\Windows\system32\kernel32.dll+0x159cd)
#15 0x0000000077b0b891 (C:\Windows\SYSTEM32\ntdll.dll+0x2b891)

svn log -r310408:310442 https://nico@llvm.org/svn/llvm-project suggests it's due to zturner's r310438 (or follow-up r310439)



Not super high priority since nobody uses lld-link atm.

Comment 1 by zturner@chromium.org, Aug 10 2017 

Would it be possible to send me the minidump and pdb of lld-link.exe? I can
try reproducing but it would be quicker if I just had the stuff. I know
what the problem is, I just need to see what type of symbol this is since
it's one we weren't expecting

Comment 2 by thakis@chromium.org, Aug 10 2017 

I don't have it. You can try to ssh into the bot (I'm off corp atm), but I'm not sure we even build with symbols there.

Comment 3 by zturner@chromium.org, Aug 10 2017 

Fair enough, I'll try linking clang with lld and see if it reproduces.

Comment 4 by zturner@chromium.org, Aug 11 2017 

Was unable to reproduce locally, so I asked Hans to initiate a clobber and
it looks like it worked?

Comment 5 by r...@chromium.org, Nov 2 2017

Status: Fixed (was: Untriaged)
We've had a successful build since then: https://build.chromium.org/p/chromium.clang/builders/CrWinClngLLDdbg/builds/32
►

Sign in to add a comment