Attaching a stack trace, using todays version of kdevelop git (kdevplatform cae5d37f9309564a3704db882518b84739760252 and kdevelop ebe44ee16d31929b9d76e0f0097c1c2f1f0ddca5).
Seems this always happens inside KDevelop::DUChainPrivate::CleanupThread::run as far as kdevelop is concerned, but the code there seems fine. Given how often this happens for me, and how few people are watching this, I'm wondering if this is some very platform specific bug (running on a pentium D here)? The crash ultimatly points to nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:216 which is in libc and is assembly for x86_64 CPUs. ** Attachment added: "Stack trace" https://bugs.launchpad.net/ubuntu/+source/kdebase/+bug/711753/+attachment/1862894/+files/kdev-trace.txt -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. https://bugs.launchpad.net/bugs/711753 Title: kdevelop crashes often -- valgrind reports oxygen invalid reads -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
