Regression(r242293:242298): clang very crashy

[Quuxplusone]

Bugzilla Link	PR24136
Status	RESOLVED WORKSFORME
Importance	P normal
Reported by	Nico Weber (nicolasweber@gmx.de)
Reported on	2015-07-15 13:14:35 -0700
Last modified on	2015-07-20 19:54:11 -0700
Version	trunk
Hardware	PC All
CC	llvm-bugs@lists.llvm.org, rafael@espindo.la, rnk@google.com
Fixed by commit(s)
Attachments	repro.zip (503670 bytes, application/zip)
Blocks
Blocked by
See also

Clang started crashing very early during a chromium build on linux, mac,
windows. Probably crashes when building anything interesting.

FAILED: ../../third_party/llvm-build/Release+Asserts/bin/clang++ -MMD -MF
obj/third_party/pdfium/fpdfsdk/src/fxedit/fxedit.fxet_ap.o.d -DOPJ_STATIC -
DV8_DEPRECATION_WARNINGS -D_CRT_SECURE_NO_WARNINGS -D_FILE_OFFSET_BITS=64 -
D_FX_CPU_=_FX_X64_ -DCHROMIUM_BUILD -DCR_CLANG_REVISION=242298 -
DCOMPONENT_BUILD -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_ASH=1 -
DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -
DUSE_X11=1 -DUSE_CLIPBOARD_AURAX11=1 -DENABLE_ONE_CLICK_SIGNIN -
DENABLE_PRE_SYNC_BACKUP -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -
DENABLE_MEDIA_ROUTER=1 -DENABLE_PEPPER_CDMS -DENABLE_CONFIGURATION_POLICY -
DENABLE_NOTIFICATIONS -DENABLE_HIDPI=1 -DENABLE_TOPCHROME_MD=1 -DUSE_UDEV -
DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -
DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -
DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1 -
DCLD_VERSION=2 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -
DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -
DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -
DENABLE_SUPERVISED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -
DV8_USE_EXTERNAL_STARTUP_DATA -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -
DSAFE_BROWSING_DB_LOCAL -DSAFE_BROWSING_SERVICE -DUSE_LIBPCI=1 -DUSE_OPENSSL=1 -
DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DNDEBUG -DNVALGRIND -
DDYNAMIC_ANNOTATIONS_ENABLED=0 -
I../../third_party/pdfium/third_party/freetype/include -Igen -fstack-protector -
-param=ssp-buffer-size=4  -pthread -fno-strict-aliasing -Wno-unused-parameter -
Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-reserved-
user-defined-literal -fcolor-diagnostics -g -
B/b/build/slave/ClangToTLinux/build/src/third_party/binutils/Linux_x64/Release/bin
-fPIC -Wheader-hygiene -Wno-char-subscripts -Wno-unneeded-internal-declaration -
Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing -Wno-
deprecated-register -Wno-inconsistent-missing-override -Wno-shift-negative-
value -Wno-overloaded-virtual -Wno-unused-variable -Wno-format -Wno-unused-
result -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -
funwind-tables -fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-
inlines-hidden -std=gnu++11 -Wno-deprecated  -c
../../third_party/pdfium/fpdfsdk/src/fxedit/fxet_ap.cpp -o
obj/third_party/pdfium/fpdfsdk/src/fxedit/fxedit.fxet_ap.o
clang-3.8: error: unable to execute command: Segmentation fault (core dumped)
clang-3.8: error: clang frontend command failed due to signal (use -v to see
invocation)
clang version 3.8.0 (trunk 242298)
Target: x86_64-unknown-linux-gnu
Thread model: posix
clang-3.8: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang-3.8: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-3.8: note: diagnostic msg: /tmp/fxet_ap-55bf1b.cpp
clang-3.8: note: diagnostic msg: /tmp/fxet_ap-55bf1b.sh
clang-3.8: note: diagnostic msg:

********************
ninja: build stopped: subcommand failed.

[Quuxplusone]

Attached repro.zip (503670 bytes, application/zip): repro

[Quuxplusone]

It doesn't crash for me with

 (trunk 242404) (llvm/trunk 242409)

[Quuxplusone]

I don't think we're seeing this anymore, right?

[Quuxplusone]

Weird, I don't remember filing this, even though it's only 5 days ago. Yes, this is no longer a problem. I guess someone fixed or reverted something.