Summary: | crash parsing a kdev-qmake project (Qt 5.5.0 qtbase.pro) | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | RJVB <rjvbertin> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | Keywords: | drkonqi |
Priority: | NOR | ||
Version First Reported In: | git master | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | macOS | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
RJVB
2015-10-13 14:49:34 UTC
looks like a kdirwatch error, or did you run out of memory? anyhow, reassigning to kdirwatch. Erm, no. The crash was in thread 10, not thread 1 (look for the KCrash entries): thread #10: tid = 0x1a771f, 0x00007fff92a46e22 libsystem_kernel.dylib`__wait4 + 10, name = 'ThreadWeaver::Thread' frame #0: 0x00007fff92a46e22 libsystem_kernel.dylib`__wait4 + 10 frame #1: 0x0000000108f340ae libkdeui.5.dylib`KCrash::startProcess(int, char const**, bool) + 286 frame #2: 0x0000000108f331d5 libkdeui.5.dylib`KCrash::defaultCrashHandler(int) + 1189 frame #3: 0x00007fff8acc65aa libsystem_platform.dylib`_sigtramp + 26 frame #4: 0x00000001281ec598 libkdev4cppduchain.dylib`DeclarationBuilder::closeDeclaration(bool) + 1800 frame #5: 0x00000001281e9ea3 libkdev4cppduchain.dylib`DeclarationBuilder::visitDeclarator(DeclaratorAST*) + 1315 frame #6: 0x00000001281d6f04 libkdev4cppduchain.dylib`ContextBuilder::visitInitDeclarator(InitDeclaratorAST*) Reassigning back to kdevelop, as the backtrace indicates. See comment #2. *** This bug has been marked as a duplicate of bug 355685 *** |