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

Issue 698841 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression

Blocking:
issue 82385



Sign in to add a comment

CrWinClangLLD bot crashing during compile

Project Member Reported by thakis@chromium.org, Mar 6 2017

Issue description

Started around Mar 1.

https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FCrWinClangLLD%2F5105%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout

C:/b/depot_tools/python276_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:./chromeexts.dll.lib /DLL /OUT:./chromeexts.dll /PDB:./chromeexts.dll.pdb @./chromeexts.dll.rsp
Assertion failed: Pos != StringRef::npos, file C:\b\rr\tmpd6vusu\w\src\third_party\llvm\tools\lld\COFF\Librarian.cpp, line 107

Wrote crash dump file "C:\Users\CHROME~1\AppData\Local\Temp\lld-link.exe-f07cb9.dmp"


The stack has no symbols and is useless, so I'm omitting it.


The bot uses these gn args:

clang_use_chrome_plugins = false
enable_nocompile_tests = false
is_chrome_branded = true
is_clang = true
is_component_build = false
is_debug = false
is_official_build = true
llvm_force_head_revision = true
strip_absolute_paths_from_debug_symbols = true
symbol_level = 1
target_cpu = "x86"
use_lld = true


You can add

clang_base_path = getenv("HOME") + "/src/llvm-build"

to make it use your locally-built clang and lld. Please take a look.
 

Comment 1 by ruiu@google.com, Mar 8 2017

Owner: ruiu@google.com
Looks like this crash is no longer happening, but https://luci-logdog.appspot.com/v/?s=chromium%2Fbb%2Fchromium.fyi%2FClangToTLinuxLLD%2F2688%2F%2B%2Frecipes%2Fsteps%2Fcompile%2F0%2Fstdout

[27308/51462] ACTION //v8:run_mkpeephole(//build/toolchain/linux:clang_x64)
FAILED: gen/v8/bytecode-peephole-table.cc 
python ../../v8/tools/run.py ./mkpeephole gen/v8/bytecode-peephole-table.cc

(bot link: https://build.chromium.org/p/chromium.fyi/builders/ClangToTLinuxLLD/builds/2688

bot args.gn:
clang_use_chrome_plugins = false
enable_nocompile_tests = false
is_clang = true
is_component_build = true
is_debug = false
llvm_force_head_revision = true
use_lld = true
)
Note that that one is on linux, while the original problem was windows.
Started here: https://build.chromium.org/p/chromium.fyi/builders/ClangToTLinuxLLD/builds/2681

Contains these two v8 rolls:
https://chromium.googlesource.com/v8/v8/+log/eea520ea..f529f7c9
https://chromium.googlesource.com/v8/v8/+log/3dd5ca1d..eea520ea

Might be due to v8 changes, not due to lld changes. But the non-lld bots are happy.
Last good clang 297295, first bad 297318 (but as I said, it's probably due to v8-side changes)

Comment 6 by r...@chromium.org, Mar 22 2017

Labels: clang
Both CrWinClangLLD and CrToTLinuxLLD are green right now, so I think this has been fixed.

Comment 7 by thakis@chromium.org, Mar 22 2017

Status: Fixed (was: Untriaged)
Yup, looks like it \o/

Sign in to add a comment