Quuxplusone / LLVMBugzillaTest

0 stars 0 forks source link

Segfault in clang::Sema::BuildDeclarationNameExpr #35732

Closed Quuxplusone closed 6 years ago

Quuxplusone commented 6 years ago
Bugzilla Link PR36759
Status RESOLVED DUPLICATE of bug 32172
Importance P normal
Reported by Justus Ranvier (justus@stashcrypto.com)
Reported on 2018-03-15 12:44:05 -0700
Last modified on 2018-03-15 15:49:16 -0700
Version 5.0
Hardware PC Linux
CC dimitry@andric.com, llvm-bugs@lists.llvm.org
Fixed by commit(s)
Attachments ActivitySummary-a21fe2.bt (7772 bytes, text/plain)
ActivitySummary-a21fe2.sh (6110 bytes, application/x-shellscript)
ActivitySummary-a21fe2.cpp.gz (632117 bytes, application/gzip)
Blocks
Blocked by
See also
Created attachment 20072
backtrace

clang50++: error: unable to execute command: Segmentation fault (core dumped)
clang50++: error: clang frontend command failed due to signal (use -v to see
invocation)
Android clang version 5.0.300080  (based on LLVM 5.0.300080)
Target: armv7a-none-linux-android
Thread model: posix
InstalledDir: /home/build/toolchain/android-ndk-r16b/armv7a/bin
clang50++: note: diagnostic msg: PLEASE submit a bug report to
http://llvm.org/bugs/ and include the crash backtrace, preprocessed source, and
associated run script.
clang50++: note: diagnostic msg:
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang50++: note: diagnostic msg: /tmp/ActivitySummary-a21fe2.cpp
clang50++: note: diagnostic msg: /tmp/ActivitySummary-a21fe2.sh
clang50++: note: diagnostic msg:

********************

Backtrace is attached.
Quuxplusone commented 6 years ago

Attached ActivitySummary-a21fe2.bt (7772 bytes, text/plain): backtrace

Quuxplusone commented 6 years ago

Attached ActivitySummary-a21fe2.sh (6110 bytes, application/x-shellscript): ActivitySummary-a21fe2.sh

Quuxplusone commented 6 years ago

Attached ActivitySummary-a21fe2.cpp.gz (632117 bytes, application/gzip): ActivitySummary-a21fe2.cpp.gz

Quuxplusone commented 6 years ago

This was fixed by https://reviews.llvm.org/rL305195 for bug 32172.

_This bug has been marked as a duplicate of bug 32172_