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

Issue 648456 link

Starred by 1 user
Status: Fixed
Owner:
h...@chromium.org
Closed: Sep 2016
Cc:
█ agutowski@google.com
h...@chromium.org
r...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 645953



Sign in to add a comment

CrWinAsan bots red

Project Member Reported by thakis@chromium.org, Sep 19 2016 
https://build.chromium.org/p/chromium.fyi/builders/CrWinAsan/builds/4125

FAILED: clang_nacl_win64/obj/sandbox/win/sandbox/sandbox_nt_util.obj 
../../third_party/llvm-build/Release+Asserts/bin/clang-cl.exe /nologo /showIncludes /FC @clang_nacl_win64/obj/sandbox/win/sandbox/sandbox_nt_util.obj.rsp /c ../../sandbox/win/src/sandbox_nt_util.cc /Foclang_nacl_win64/obj/sandbox/win/sandbox/sandbox_nt_util.obj /Fd"clang_nacl_win64/obj/sandbox/win/sandbox_cc.pdb"
Assertion failed: !NodePtr->isKnownSentinel(), file C:\b\c\b\CrWinAsan\src\third_party\llvm\include\llvm/ADT/ilist_iterator.h, line 126
Wrote crash dump file "C:\Users\CHROME~1\AppData\Local\Temp\clang-cl.exe-7a9dd9.dmp"
#0 0x0000000140e54eb5 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x10f4eb5)
#1 0x000000014242ca8e (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26cca8e)
#2 0x000000014241e4fc (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26be4fc)
#3 0x0000000142419b7a (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26b9b7a)
#4 0x0000000142419c16 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26b9c16)
#5 0x0000000140ec353c (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x116353c)
#6 0x0000000140f25873 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x11c5873)
#7 0x0000000140f27f1c (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x11c7f1c)
#8 0x0000000140f24e1a (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x11c4e1a)
#9 0x0000000140d6510b (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x100510b)
#10 0x0000000140d67b7d (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1007b7d)
#11 0x0000000140d6861c (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x100861c)
#12 0x0000000140af1ccd (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0xd91ccd)
#13 0x0000000140af13c0 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0xd913c0)
#14 0x0000000140af126c (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0xd9126c)
#15 0x00000001410366b8 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x12d66b8)
#16 0x00000001410368f0 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x12d68f0)
#17 0x000000014255ef2e (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x27fef2e)
#18 0x000000014135bddc (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x15fbddc)
#19 0x00000001419650f6 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x1c050f6)
#20 0x0000000141324c9b (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x15c4c9b)
#21 0x000000014255e8a8 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x27fe8a8)
#22 0x0000000141324b38 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x15c4b38)
#23 0x00000001413169bc (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x15b69bc)
#24 0x000000014138de69 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x162de69)
#25 0x000000013fdbf474 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x5f474)
#26 0x000000013fdbb3c4 (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x5b3c4)
#27 0x000000013fdbd3bf (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x5d3bf)
#28 0x000000014241515d (C:\b\c\b\CrWinAsan\src\third_party\llvm-build\Release+Asserts\bin\clang-cl.exe+0x26b515d)
#29 0x0000000076c659cd (C:\Windows\system32\kernel32.dll+0x159cd)
#30 0x0000000076e9b891 (C:\Windows\SYSTEM32\ntdll.dll+0x2b891)

Comment 1 by thakis@chromium.org, Sep 20 2016

Cc: agutowski@google.com h...@chromium.org
agutowski volunteered to look at this.

If you look for "got_clang_revision" on https://build.chromium.org/p/chromium.fyi/builders/CrWinAsan/builds/4125 , you'll get 281899 . On the prior, green, build (https://build.chromium.org/p/chromium.fyi/builders/CrWinAsan/builds/4124) we have 281879. So something in clang 281879:281899 caused this.

https://build.chromium.org/p/chromium.fyi/builders/CrWinAsan/builds/4125/steps/generate_build_files/logs/stdio gives you the exact chrome build config that that bot uses. https://build.chromium.org/p/chromium.fyi/builders/CrWinAsan shows that the latest build that bot did is still broken. https://build.chromium.org/p/chromium.fyi/console?category=clang%20tot shows that the other win/asan bots are unhappy as well.

Comment 2 by thakis@chromium.org, Sep 21 2016

Blocking: 645953

Comment 3 by thakis@chromium.org, Sep 21 2016 

Hey, Hans independently rediscovered this here: https://llvm.org/bugs/show_bug.cgi?id=30468

Comment 4 by h...@chromium.org, Sep 21 2016 

Should be fixed with Clang r282077

Comment 5 by thakis@chromium.org, Sep 21 2016

Owner: h...@chromium.org
Status: Fixed (was: Untriaged)
►

Sign in to add a comment