Version: 3.5.0 (using KDE KDE 3.5.8) Installed from: Ubuntu Packages Compiler: gcc 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) libraries: x86_64-linux-gnu OS: Linux Kdevelop crashes when creating a c++ Project. Description : ------------- Hello, starting kdevelop goes fine, but when creating a c/c++ project, once i click the "finished" button, looks like during the loading of the debugger plugin it crashes. I assume it's gdb, because creating a java projects, or a php one did go smoothly. I am using standard installation. (through kubuntu stable) Versions : ---------- # gdb -v GNU gdb 6.6-debian ... This GDB was configured as "x86_64-linux-gnu". Software: --------- # uname -a Linux XsP5E 2.6.22-14-generic #1 SMP Tue Dec 18 05:28:27 UTC 2007 x86_64 GNU/Linux Hardware: --------- Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz Backtrace : ----------- (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) .. ## lot's of these ## .. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47015107908560 (LWP 12165)] [New Thread 1090525520 (LWP 12383)] [New Thread 1082132816 (LWP 12373)] [KCrash handler] #5 0x00002ac285537765 in raise () from /lib/libc.so.6 #6 0x00002ac2855391c0 in abort () from /lib/libc.so.6 #7 0x00002ac284e317b4 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #8 0x00002ac284e2f746 in ?? () from /usr/lib/libstdc++.so.6 #9 0x00002ac284e2f773 in std::terminate () from /usr/lib/libstdc++.so.6 #10 0x00002ac284e2f85a in __cxa_throw () from /usr/lib/libstdc++.so.6 #11 0x00002ac284e2fd19 in operator new () from /usr/lib/libstdc++.so.6 #12 0x00002ac284e2fdd9 in operator new[] () from /usr/lib/libstdc++.so.6 #13 0x00002ac286f26c66 in QString::setLength () from /usr/lib/libqt-mt.so.3 #14 0x00002ac286f2ed8d in operator>> () from /usr/lib/libqt-mt.so.3 #15 0x00002ac29782c577 in Tag::load () from /usr/lib/libkdevcatalog.so.0 #16 0x00002ac29782e9ba in Catalog::query () from /usr/lib/libkdevcatalog.so.0 #17 0x00002ac29745700e in CodeInformationRepository::query () from /usr/lib/kde3/libkdevcppsupport.so #18 0x00002ac2974dc1c6 in CppSupportPart::buildSafeFileSet () from /usr/lib/kde3/libkdevcppsupport.so #19 0x00002ac2974ea119 in CppSupportPart::qt_invoke () from /usr/lib/kde3/libkdevcppsupport.so #20 0x00002ac286c25d76 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #21 0x00002ac286c26910 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #22 0x00002ac286f959a2 in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #23 0x00002ac286c4c257 in QTimer::event () from /usr/lib/libqt-mt.so.3 #24 0x00002ac286bc12a2 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #25 0x00002ac286bc3031 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #26 0x00002ac2862c3308 in KApplication::notify () from /usr/lib/libkdecore.so.4 #27 0x00002ac286b53d12 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #28 0x00002ac286bb455c in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #29 0x00002ac286b68443 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #30 0x00002ac286bda7e7 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #31 0x00002ac286bda5ef in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #32 0x00002ac286bc2d68 in QApplication::exec () from /usr/lib/libqt-mt.so.3 #33 0x000000000040780b in ?? () #34 0x00002ac285523b44 in __libc_start_main () from /lib/libc.so.6 #35 0x0000000000406fc9 in ?? () #36 0x00007fff261e4b88 in ?? () #37 0x0000000000000000 in ?? () Console gives this : -------------------- xsmarty@XsP5E:~$ kdevelop QObject::connect: No such slot MakeWidget::slotDocumentOpened(const KURL&) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'make widget') QLayout "unnamed" added to IndexView "unnamed", which already has a layout kdecore (KAction): WARNING: KAction::initPrivate(): trying to assign a shortcut (Alt+Ctrl+Shift+N) to an unnamed action. kdecore (KProcess): WARNING: _attachPty() 12 QImage::smoothScale: Image is a null image kio (KTrader): WARNING: Parsing ' and [X-KDevelop-Version] == 4' gave syntax error kio (KTrader): WARNING: Parsing ' and [X-KDevelop-Version] == 4' gave syntax error QObject::connect: No such signal KListBox::clicked(QListBoxItem*item) QObject::connect: (sender name: 'srcDistFileListBox') QObject::connect: (receiver name: 'dist_widget') QObject::connect: No such slot GDBDebugger::GDBBreakpointWidget::slotAddBlankBreakpoint() QObject::connect: (sender name: 'gdbBreakpointWidget') QObject::connect: (receiver name: 'gdbBreakpointWidget') kio (KTrader): WARNING: Parsing ' and [X-KDevelop-Version] == 4' gave syntax error kio (KTrader): WARNING: Parsing ' and [X-KDevelop-Version] == 4' gave syntax error QObject::connect: No such slot ProblemReporter::configWidget(KDialogBase*) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'problemReporterWidget') ASSERT: "part && parent" in /build/buildd/kdevelop-3.5.0/./parts/fileview/partwidget.cpp (41) kio (KTrader): WARNING: Parsing ' and [X-KDevelop-Version] == 4' gave syntax error kio (KTrader): WARNING: Parsing ' and [X-KDevelop-Version] == 4' gave syntax error terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc KCrash: Application 'kdevelop' crashing...
Does it matter which c++ project template you choose? Did you do any other changes? The backtrace as well as the debug output indicate that this might be a problem of your system, specifically it seems that either you ran out of memory or you have some bad memory installed.
Are you sure you are using the newest version of KDevelop? I remember that there was such a problem in the place indicated by the backtrace, but that it was fixed.
Andreas: - i tried this with automake based, custom make, simple console app. Same problem. - kcachegrind, valgrind and graphviz where also installed at the same time with this kdevelop. - From what i think, given my 2Gb of ram already memtested(vista memtest), i don't think it comes from a memory problem.. (i have very high quality ddr2-800 444-12), but i could make another memtest(ubuntu memtest) run just to be really sure. David: Version: 3.5.0 (using KDE 3.5.8). Don't know if there is a more recent one.it just comes with my distribution (ubuntu stable 7.10 gutsy). But: I don't understand the '[X-KDevelop-Version] == 4' error in console, Looks like it is trying to add the debugger panel then crashes for this reason. Could it be a problem between 32bit libs and 64bit ones ? is there a way for me to add more debug messages to know which library is called ? Thx.
Ok, I don't think another run of memtest is needed. Yes this very much looks like a 64-bit issue, there's somebody on the kdevelop list with exactly the same backtrace, who just updated his kdevelop packages on fedora core 8. I have 0 idea though what to do about it, the crash is deep inside the C++ standard lib and obviously happens while doing something in kdevelops c++ plugin (not the debugger).
On the mailinglist the problem could be resolved after removing the existing PCS databases in $HOME/.kde/share/apps/kdevcppsupport/pcs. If that directory is empty for you, don't worry that just means you never used the class-importer.
Removing the existing PCS databases in $HOME/.kde/share/apps/kdevcppsupport/pcs did solve the problem, many thanks Andreas. Should i state this bug report as resolved ? it still is a bug ..
Yes, it is still a bug, but I suspect the bug is within the berkley db, not inside KDevelop. Did you upgrade your berkley db library recently? Sometimes berkley db even decides to completely trash the files it has open. I agree that kdevelop crashing when this happens is not nice, but IIRC David tried very hard to find all occurences of problems due to broken pcs files. And looking at the backtrace we can hardly do anything about new completely breaking down.