https://bugs.kde.org/show_bug.cgi?id=378442

--- Comment #2 from Kevin Funk <kf...@kde.org> ---
Pasting relevant stack trace inline so it doesn't get lost:

Thread 11 (Thread 0x7f4a2d109700 (LWP 8487)):
[KCrash Handler]
#6  0x00007f4a7d5ac6ce in raise () from /lib64/libc.so.6
#7  0x00007f4a7d5adbdd in abort () from /lib64/libc.so.6
#8  0x00007f4a7d5a5377 in ?? () from /lib64/libc.so.6
#9  0x00007f4a7d5a5422 in __assert_fail () from /lib64/libc.so.6
#10 0x00007f4a2fabcea0 in clang::Parser::~Parser() () from
/usr/lib64/llvm/4/lib64/../lib64/../lib64/libclangParse.so.4
#11 0x00007f4a2fabcea9 in clang::Parser::~Parser() () from
/usr/lib64/llvm/4/lib64/../lib64/../lib64/libclangParse.so.4
#12 0x00007f4a698979d1 in llvm::CrashRecoveryContext::~CrashRecoveryContext()
() from /usr/lib/llvm/4/lib64/libLLVMSupport.so.4
#13 0x00007f4a4d78760d in clang_reparseTranslationUnit () from
/usr/lib64/llvm/4/lib64/libclang.so.4
#14 0x00007f4a4f13eb81 in ParseSession::reparse(QVector<UnsavedFile> const&,
ClangParsingEnvironment const&) () from /usr/lib64/libKDevClangPrivate.so.27
#15 0x00007f4a5d4289c4 in ?? () from
/usr/lib64/qt5/plugins/kdevplatform/27/kdevclangsupport.so
#16 0x00007f4a7948cf8f in
ThreadWeaver::IdDecorator::run(QSharedPointer<ThreadWeaver::JobInterface>,
ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5
#17 0x00007f4a7948d5d6 in
ThreadWeaver::Executor::run(QSharedPointer<ThreadWeaver::JobInterface> const&,
ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5
#18 0x00007f4a7948bf80 in
ThreadWeaver::Job::execute(QSharedPointer<ThreadWeaver::JobInterface> const&,
ThreadWeaver::Thread*) () from /usr/lib64/libKF5ThreadWeaver.so.5
#19 0x00007f4a7948ba0e in ThreadWeaver::Thread::run() () from
/usr/lib64/libKF5ThreadWeaver.so.5
#20 0x00007f4a7dc5dcdb in ?? () from /usr/lib64/libQt5Core.so.5
#21 0x00007f4a7b0d9286 in start_thread () from /lib64/libpthread.so.0
#22 0x00007f4a7d66347f in clone () from /lib64/libc.so.6

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to