Version: 3.0.0a7 (using KDE 3.1.9) Compiler: gcc version 3.3.2 20030908 (Debian prerelease) OS: Linux (i686) release 2.6.0-test4 I make a new c++/kde/Application-Framework. When i try to run it KDevelop crashes. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 10226)] 0x40d3c608 in posix_memalign () from /usr/lib/libkdecore.so.4 (gdb) bt #0 0x40d3c608 in posix_memalign () from /usr/lib/libkdecore.so.4 #1 0x40d3bfb6 in malloc () from /usr/lib/libkdecore.so.4 #2 0x4167e57e in operator new(unsigned) () from /usr/lib/libstdc++.so.5 #3 0x4130d102 in QString::QString(int, bool) () from /usr/lib/libqt-mt.so.3 #4 0x4131115c in QString::mid(unsigned, unsigned) const () from /usr/lib/libqt-mt.so.3 #5 0x41321842 in QStringList::split(QString const&, QString const&, bool) () from /usr/lib/libqt-mt.so.3 #6 0x4132152b in QStringList::split(QChar const&, QString const&, bool) () from /usr/lib/libqt-mt.so.3 #7 0x40556f2c in DomUtil::elementByPath(QDomDocument const&, QString const&) ( doc=@0x89d1d68, path=@0xbfffef00) at domutil.cpp:30 #8 0x40557168 in DomUtil::readEntryAux(QDomDocument const&, QString const&) ( doc=@0x89d1d68, path=@0xbfffef00) at domutil.cpp:58 #9 0x405572c0 in DomUtil::readBoolEntry(QDomDocument const&, QString const&, bool) ( doc=@0x89d1d68, path=@0xbfffef00, defaultEntry=false) at domutil.cpp:77 #10 0x4261a48e in AutoProjectPart::slotExecute2() (this=0x8a8eb00) at autoprojectpart.cpp:1018 #11 0x4261a18d in AutoProjectPart::slotExecute() (this=0x8a8eb00) at autoprojectpart.cpp:978 #12 0x4261ad7a in AutoProjectPart::slotCommandFinished(QString const&) (this=0x8a8eb00, command=@0x8818cf0) at autoprojectpart.cpp:1099 #13 0x4261b366 in AutoProjectPart::qt_invoke(int, QUObject*) (this=0x8a8eb00, _id=18, _o=0xbffff190) at autoprojectpart.moc:144 #14 0x4106dc5c in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #15 0x4106e0fd in QObject::activate_signal(int, QString) () from /usr/lib/libqt-mt.so.3 #16 0x405301fe in KDevMakeFrontend::commandFinished(QString const&) (this=0x826f6a8, t0=@0x8213870) at kdevmakefrontend.moc:90 #17 0x41e72344 in MakeWidget::slotProcessExited(KProcess*) (this=0x8213678) at makewidget.cpp:516 #18 0x41e73a11 in MakeWidget::qt_invoke(int, QUObject*) (this=0x8213678, _id=158, _o=0xbffff310) at makewidget.moc:155 #19 0x4106dc5c in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #20 0x40c7c91a in KProcess::processExited(KProcess*) () from /usr/lib/libkdecore.so.4 #21 0x40c7b5cc in KProcess::processHasExited(int) () from /usr/lib/libkdecore.so.4 #22 0x40c7dcdc in KProcessController::slotDoHousekeeping() () from /usr/lib/libkdecore.so.4 #23 0x40c7e049 in KProcessController::qt_invoke(int, QUObject*) () ---Type <return> to continue, or q <return> to quit--- from /usr/lib/libkdecore.so.4 #24 0x4106dc5c in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/libqt-mt.so.3 #25 0x4106ddbd in QObject::activate_signal(int, int) () from /usr/lib/libqt-mt.so.3 #26 0x4134e262 in QSocketNotifier::activated(int) () from /usr/lib/libqt-mt.so.3 #27 0x410897b0 in QSocketNotifier::event(QEvent*) () from /usr/lib/libqt-mt.so.3 #28 0x4101657f in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #29 0x41015b8b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3 #30 0x40c32c82 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #31 0x410064aa in QEventLoop::activateSocketNotifiers() () from /usr/lib/libqt-mt.so.3 #32 0x40fc5f48 in QEventLoop::processEvents(unsigned) () from /usr/lib/libqt-mt.so.3 #33 0x4102839f in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3 #34 0x41028254 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3 #35 0x410167c1 in QApplication::exec() () from /usr/lib/libqt-mt.so.3 #36 0x0806964f in main (argc=1, argv=0xbffffbf4) at main.cpp:126
I experience the same type of crash. I downloaded from cvs, 2003-10-03, 1415 UTC Made a release-build according to instructions on cvs pages. No error messages. $ kdevelop --version Qt: 3.1.1 KDE: 3.1-12 Red Hat KDevelop: 3.0.0a7 -------- System info--------- KDEDIR=/usr LD_LIBRARY_PATH=/usr/lib/qt-3.1/lib:/usr/lib: LIBRARY_PATH=/usr/lib/qt-3.1/lib:/usr/lib: PATH=/usr/lib/qt-3.1/bin:/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin: /home/x/bin QTDIR=/usr/lib/qt-3.1 gcc (GCC) 3.2.2 20030222 (Red Hat Linux 3.2.2-5) kernel: 2.4.20-20.9 RedHat 9.0 system, all updates. -------- Sys info end ---------- Crash report: I did the same as above described. New C++ console "Hello World" etc.... kdevelop crashes immediately after execute program within kdevelop. Running the program from an xterm works fine. --------------- Backtrace start ------------ [New Thread 1096914624 (LWP 10097)] [New Thread 1116949808 (LWP 10130)] 0xffffe002 in ?? () #0 0xffffe002 in ?? () #1 0x40a6c57d in KCrash::defaultCrashHandler(int) () from /usr/lib/libkdecore.so.4 #2 <signal handler called> #3 0x4207c45c in memcpy () from /lib/tls/libc.so.6 #4 0x41143b2b in QString::operator+=(QString const&) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #5 0x41eae909 in AutoProjectPart::slotExecute2() () from /usr/lib/kde3/libkdevautoproject.so #6 0x41eae22f in AutoProjectPart::slotExecute() () from /usr/lib/kde3/libkdevautoproject.so #7 0x41eb018b in AutoProjectPart::qt_invoke(int, QUObject*) () from /usr/lib/kde3/libkdevautoproject.so #8 0x40ec30c9 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #9 0x40ec2f6d in QObject::activate_signal(int) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #10 0x4082ec7b in KAction::activated() () from /usr/lib/libkdeui.so.4 #11 0x4082010f in KAction::slotActivated() () from /usr/lib/libkdeui.so.4 #12 0x4082ee81 in KAction::qt_invoke(int, QUObject*) () from /usr/lib/libkdeui.so.4 #13 0x40ec30c9 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #14 0x411a2452 in QSignal::signal(QVariant const&) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #15 0x40edd158 in QSignal::activate() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #16 0x40faf97d in QPopupMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #17 0x40ef700c in QWidget::event(QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #18 0x40e64f24 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #19 0x40e64753 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #20 0x40a001e9 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #21 0x40e0ad7d in QETWidget::translateMouseEvent(_XEvent const*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #22 0x40e08cdf in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #23 0x40e1dbda in QEventLoop::processEvents(unsigned) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #24 0x40e78cf6 in QEventLoop::enterLoop() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #25 0x40e78b98 in QEventLoop::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #26 0x40e65151 in QApplication::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #27 0x08067a77 in main () #28 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6 -------- Backtrace end: ---------------------- In the xterm where I started kdevelop I got these: $ kdevelop QObject::connect: No such slot FileTreeWidget::slotToggleShowVCSFields() QObject::connect: (sender name: 'actiontoggleshowvcsfieldstoggleaction') QObject::connect: (receiver name: 'unnamed') QObject::connect: No such signal KateDocument::fileNameChanged(const KURL&) QObject::connect: (sender name: 'Kate::Document') QObject::connect: (receiver name: 'unnamed') $ ------------------------------- Regards Svein
Confirmed, I have it too. Executing the KDevelop project from KDevelop works fine, executing a fresh "Simple Hello World" project does not.
*** This bug has been marked as a duplicate of 65322 ***