Summary: | KDevelop crashed suddenly during building of CMake project [MakeJob::start] | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Alexey Chernov <4ernov> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | kevin.clevenger, mmdanziger, mwoehlke.floss, wolfstep |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | 4.3.0 | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | New crash information added by DrKonqi |
Description
Alexey Chernov
2012-08-27 09:02:40 UTC
It seems that the problem appears if: 1. You added a project to selection during this session. 2. The project needs to be CMake-configured before build. So, obviously as soon as CMake finishes configuration, KDevelop crashes. Created attachment 74927 [details] New crash information added by DrKonqi kdevelop (4.4.0) on KDE Platform 4.9.2 using Qt 4.8.2 - What I was doing when the application crashed: KDevelop crashed while rebuilding my project. Contrary to comment #1, I don't believe I had changed the project selection during the session, or that CMake needed to re-run as part of the build. (On the other hand, I've also told KDevelop that 'make' is spelled "ninja", which is also a little different from the original report.) -- Backtrace (Reduced): #6 0x00007fbed8c19b4e in MakeJob::start (this=0xabc36c0) at /usr/src/debug/kdevelop-4.4.0/projectbuilders/makebuilder/makejob.cpp:94 #7 0x00007fbf0acb2135 in KDevelop::RunController::registerJob (this=0x29a9820, job=0x0) at /usr/src/debug/kdevplatform-1.4.0/shell/runcontroller.cpp:566 [...] #9 0x00000038aa133e32 in KJob::result (this=this@entry=0xa7baec0, _t1=_t1@entry=0xa7baec0) at /usr/src/debug/kdelibs-4.9.2/x86_64-redhat-linux-gnu/kdecore/kjob.moc:207 #10 0x00000038aa133e70 in KJob::emitResult (this=0xa7baec0) at /usr/src/debug/kdelibs-4.9.2/kdecore/jobs/kjob.cpp:318 #11 0x00007fbed8a03d67 in CMakeJob::slotCompleted (this=0xa7baec0) at /usr/src/debug/kdevelop-4.4.0/projectbuilders/cmakebuilder/cmakejob.cpp:127 Actually, per bug 309402, I guess CMake did get run. Also, after attaching the backtrace, I had this happen 3-4 more times in immediate succession; just opened the same session and immediately tried to build it. But since that I'm unable to reproduce (not at least as reliably as the first few times). If you can reproduce this with current master (that code here has changed a bit there), please reopen bug 238765. Also, if possible, try to run kdevelop through valgrind to get a better log. *** This bug has been marked as a duplicate of bug 238765 *** *** Bug 309650 has been marked as a duplicate of this bug. *** *** Bug 310778 has been marked as a duplicate of this bug. *** *** Bug 313934 has been marked as a duplicate of this bug. *** |