Summary: | Crash while building cmake project [MakeJob::start, KDevelop::RunController::registerJob] | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Anton <bond-cash> |
Component: | general | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | 4ernov, apcomptec, bugs, daviddoria, dmayerich, findshiva, jorti, justin, oss |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
Description
Anton
2010-05-25 09:26:15 UTC
If this is reproduceable please run kdevelop in valgrind like this: KDEV_SESSION=blah valgrind --trace-origins=yes kdevelop.bin and post the valgrind log. Valgrind says: Bad option '--trace-origins=yes'; aborting. I tried to run: KDEV_SESSION=blah valgrind --track-origins=yes /usr/bin/kdevelop.bin But: valgrind: m_debuginfo/readelf.c:1898 (vgModuleLocal_read_elf_debug_info): Assertion 'di->bss_size == shdr->sh_size' failed. ==22950== at 0x3802DF6D: ??? (in /usr/lib/valgrind/memcheck-x86-linux) sched status: running_tid=0 I'm not good in debugging, what shoud I do? Another crash happens. I am writing science project: port of Matlab code to C. In same file (over 300 lines) lives C and old Matlab code. When I finished porting some function, I was trying to delete over 100 lines of Matlab code: accentuate it and on press delete button crash happens. Bug is always reproducible. Waiting for instructions. *** Bug 242709 has been marked as a duplicate of this bug. *** *** Bug 305860 has been marked as a duplicate of this bug. *** I think this has been fixed in current master, at least I can't manage to crash using the new builderjob code path. If you can still reproduce it, please run kdevelop through valgrind and show us a log. Or tell us how to reproduce it exactly. *** Bug 309220 has been marked as a duplicate of this bug. *** *** Bug 308988 has been marked as a duplicate of this bug. *** *** Bug 311287 has been marked as a duplicate of this bug. *** Created attachment 75922 [details]
New crash information added by DrKonqi
kdevelop (4.4.1) on KDE Platform 4.9.4 using Qt 4.8.3
- What I was doing when the application crashed:
clicked the "build" button (or hit F8); I was using a custom CMakeLists.txt which works from the shell
-- Backtrace (Reduced):
#7 0x00007ffc328d6a71 in MakeJob::start (this=0x647da50) at ../../../projectbuilders/makebuilder/makejob.cpp:94
#8 0x00007ffc6ead1655 in KDevelop::RunController::registerJob (this=0x15f2210, job=0x0) at ../../shell/runcontroller.cpp:566
[...]
#10 0x00007ffc6f08def2 in KJob::result (this=this@entry=0x6a2b6c0, _t1=_t1@entry=0x6a2b6c0) at ./kjob.moc:208
#11 0x00007ffc6f08df30 in KJob::emitResult (this=0x6a2b6c0) at ../../kdecore/jobs/kjob.cpp:318
#12 0x00007ffc326c0cb7 in CMakeJob::slotCompleted (this=0x6a2b6c0) at ../../../projectbuilders/cmakebuilder/cmakejob.cpp:127
*** Bug 313253 has been marked as a duplicate of this bug. *** *** Bug 315420 has been marked as a duplicate of this bug. *** *** Bug 315785 has been marked as a duplicate of this bug. *** Created attachment 77804 [details]
New crash information added by DrKonqi
kdevelop (4.4.1) on KDE Platform 4.9.4 using Qt 4.8.3
- What I was doing when the application crashed:
I was building a CMake project. The crash occured during the CMake portion of the build.
-- Backtrace (Reduced):
#7 0x00007f12c5860a71 in MakeJob::start (this=0x56b56d0) at ../../../projectbuilders/makebuilder/makejob.cpp:94
#8 0x00007f12f9cdd655 in KDevelop::RunController::registerJob (this=0x291a080, job=0x1) at ../../shell/runcontroller.cpp:566
[...]
#10 0x00007f12fa29bef2 in KJob::result (this=this@entry=0x5743e00, _t1=_t1@entry=0x5743e00) at ./kjob.moc:208
#11 0x00007f12fa29bf30 in KJob::emitResult (this=0x5743e00) at ../../kdecore/jobs/kjob.cpp:318
#12 0x00007f12c5648cb7 in CMakeJob::slotCompleted (this=0x5743e00) at ../../../projectbuilders/cmakebuilder/cmakejob.cpp:127
merging with bug 302413 which was reopened - apparently still an issue. *** This bug has been marked as a duplicate of bug 302413 *** |