clang.exe: error: clang frontend command failed due to signal (mozilla plugin crash)
Categories
(Developer Infrastructure :: Source Code Analysis, defect, P2)
Tracking
(firefox70 fixed)
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: mayhemer, Assigned: andi)
References
Details
Attachments
(2 files)
|
1.14 KB,
patch
|
Details | Diff | Splinter Review | |
|
47 bytes,
text/x-phabricator-request
|
Details | Review |
Comment 1•7 years ago
|
||
| Reporter | ||
Comment 2•7 years ago
|
||
Comment 3•7 years ago
|
||
Andi, can you reproduce this issue?
| Assignee | ||
Comment 4•7 years ago
|
||
No, unfortunately I cannot, and neither looking other the build artifacts that we have for this crash. Indeed we don't build with debug symbols, but maybe because they are stripped since we do pgo and opt?
Anyway this shouldn't be a blocker you can just disable static-analysis altogether.
mayhemer have you tried this?
| Reporter | ||
Comment 5•7 years ago
|
||
The E->getType()-> dereference returns null, there is no type for the expression.
| Reporter | ||
Updated•7 years ago
|
Comment 6•7 years ago
•
|
||
I happens to me when I was using MacOS to build Android Firefox with optimized non-debug build, and the workaround patch doesn't work to me.
Comment 7•7 years ago
|
||
(In reply to Daosheng Mu[:daoshengmu] from comment #6)
I happens to me when I was using MacOS to build Android Firefox with optimized non-debug build, and the workaround patch doesn't work to me.
Log messages:
4:14.68 clang++: error: unable to execute command: Segmentation fault: 11
4:14.68 clang++: error: clang frontend command failed due to signal (use -v to see invocation)
4:14.69 Android (4691093 based on r316199) clang version 6.0.2 (https://android.googlesource.com/toolchain/clang 183abd29fc496f55536e7d904e0abae47888fc7f) (https://android.googlesource.com/toolchain/llvm 34361f192e41ed6e4e8f9aca80a4ea7e9856f327) (based on LLVM 6.0.2svn)
4:14.69 Target: arm--linux-android
4:14.69 Thread model: posix
4:14.69 InstalledDir: /Users/daoshengmu/.mozbuild/android-ndk-r17b/toolchains/llvm/prebuilt/darwin-x86_64/bin
4:14.69 clang++: note: diagnostic msg: PLEASE submit a bug report to http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and associated run script.
4:15.08 clang++: note: diagnostic msg:
4:15.08 ********************
4:15.08 PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
4:15.08 Preprocessed source(s) and associated run script(s) are located at:
4:15.08 clang++: note: diagnostic msg: /var/folders/jt/42zfccf178q5h8nknxgft5fr0000gn/T/Unified_cpp_js_src_jit4-b359d3.cpp
4:15.08 clang++: note: diagnostic msg: /var/folders/jt/42zfccf178q5h8nknxgft5fr0000gn/T/Unified_cpp_js_src_jit4-b359d3.sh
4:15.08 clang++: note: diagnostic msg: Crash backtrace is located in
4:15.08 clang++: note: diagnostic msg: /Users/daoshengmu/Library/Logs/DiagnosticReports/clang++_<YYYY-MM-DD-HHMMSS>_<hostname>.crash
4:15.08 clang++: note: diagnostic msg: (choose the .crash file that corresponds to your crash)
4:15.08 clang++: note: diagnostic msg:
4:15.08 ********************
4:15.08 make[4]: *** [Unified_cpp_js_src_jit4.o] Error 254
4:15.08 make[4]: *** Waiting for unfinished jobs....
| Reporter | ||
Updated•7 years ago
|
| Assignee | ||
Comment 9•6 years ago
•
|
||
It is possible that in that particular case QualType doesn't point yet to a Type so verifying it's sanity it's legit, but a refactoring to this checker should be more appropriate so most of the refinement of the matching should be done from the actual matcher and not after the matcher matched a node and after that we discard that mode.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=e10f68746cd91ad273ba007ef5d04722a4837fec
| Assignee | ||
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
| bugherder | ||
Updated•3 years ago
|
Description
•