I have successfully emerged kdevelop and the application appears to run with no problems. When inside KDevelop 3.0b2 I decided to follow the tutorial on how to create a simple KDE application. From the Project menu I selected new project, then selected a "Simple KDE Application" as the project option. I proceded to fill out the information as described in the tutorial, clicked on Next a couple of times and then clicked Finish. The KDevelop program appeared to be creating the application and I could see activity in the message window. I can just see it report that it is finished when the program crashes and I see the KDE crash handler. Reproducible: Always Steps to Reproduce: 1.emerge kdevelop 2.Run KDevelop and start a new project. 3.Select any project you like. 4.Fill out the wizard with anything you like and click on finish. 5. KDevelop crashes. Actual Results: KDE Crash handler reported that kdevelop caused a signal 11. The backtrace information is as follows... (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 12443)] [New Thread 32769 (LWP 12449)] [New Thread 16386 (LWP 12450)] 0x416cba2b in waitpid () from /lib/libpthread.so.0 #0 0x416cba2b in waitpid () from /lib/libpthread.so.0 #1 0x40e220ac in __JCR_LIST__ () from /usr/kde/3.2/lib/libkdecore.so.4 Expected Results: I would expect to see KDevelop leave me with the source code showing for the project that I had just created using the wizard. I am useing gentoo which I regually update. The Linux kernel is slightly older at 2.4.22-gentoo-test-r1. I am running the latest KDE 3.2 (3.1.94) and KDevelop 3.0b2. bash-2.05b# emerge info Portage 2.0.49-r20 (default-x86-1.4, gcc-3.3.2, glibc-2.3.3_pre20031222-r0, 2.4.22-gentoo-test-r1) ================================================================= System uname: 2.4.22-gentoo-test-r1 i686 Intel(R) Pentium(R) III Mobile CPU 1000MHz Gentoo Base System version 1.4.3.12 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CFLAGS="-O3 -mcpu=pentium3 -funroll-loops -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -mcpu=pentium3 -funroll-loops -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox" GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gpm gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mpeg mysql ncurses nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib" bash-2.05b#
I also have the same problem, although after I click finish I don't see the messages run by. My backtrace is: (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 30983)] [New Thread 32769 (LWP 30994)] 0x4165889a in waitpid () from /lib/libpthread.so.0 #0 0x4165889a in waitpid () from /lib/libpthread.so.0 #1 0x40d3401d in KCrash::defaultCrashHandler(int) () from /usr/kde/3.2/lib/libkdecore.so.4 #2 0x41657635 in __pthread_sighandler () from /lib/libpthread.so.0 #3 <signal handler called> #4 0x40b6515c in KDockWidget::mayBeHide() const () from /usr/kde/3.2/lib/libkdeui.so.4 #5 0x404e05ec in KMDIPrivate::ToggleToolViewAction::anDWChanged() () from /usr/kde/3.2/lib/libkmdi.so.1 #6 0x404e0298 in KMDIPrivate::ToggleToolViewAction::qt_invoke(int, QUObject*) () from /usr/kde/3.2/lib/libkmdi.so.1 #7 0x410eb3d9 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/qt/3/lib/libqt-mt.so.3 #8 0x410eb28c in QObject::activate_signal(int) () from /usr/qt/3/lib/libqt-mt.so.3 #9 0x40b72e4b in KDockManager::change() () from /usr/kde/3.2/lib/libkdeui.so.4 #10 0x40b62fae in KDockWidget::event(QEvent*) () from /usr/kde/3.2/lib/libkdeui.so.4 #11 0x410928fd in QApplication::internalNotify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #12 0x41091ce9 in QApplication::notify(QObject*, QEvent*) () from /usr/qt/3/lib/libqt-mt.so.3 #13 0x40ca516e in KApplication::notify(QObject*, QEvent*) () from /usr/kde/3.2/lib/libkdecore.so.4 #14 0x4111bdde in QWidget::show() () from /usr/qt/3/lib/libqt-mt.so.3 #15 0x40b62e19 in KDockWidget::show() () from /usr/kde/3.2/lib/libkdeui.so.4 #16 0x4111c391 in QWidget::showChildren(bool) () from /usr/qt/3/lib/libqt-mt.so.3 #17 0x4111bcc9 in QWidget::show() () from /usr/qt/3/lib/libqt-mt.so.3 #18 0x412188da in QWidgetStack::show() () from /usr/qt/3/lib/libqt-mt.so.3 #19 0x404d92a1 in KMdiDockContainer::tabClicked(int) () from /usr/kde/3.2/lib/libkmdi.so.1 #20 0x404d8571 in KMdiDockContainer::insertWidget(KDockWidget*, QPixmap, QString const&, int&) () from /usr/kde/3.2/lib/libkmdi.so.1 #21 0x40b6358b in KDockWidget::manualDock(KDockWidget*, KDockWidget::DockPosition, int, QPoint, bool, int) () from /usr/kde/3.2/lib/libkdeui.so.4 #22 0x40b632ee in KDockWidget::manualDock(KDockWidget*, KDockWidget::DockPosition, int, QPoint, bool, int) () from /usr/kde/3.2/lib/libkdeui.so.4 #23 0x0806757d in ?? () #24 0x0828da50 in ?? () #25 0x0816ee38 in ?? () #26 0x00000008 in ?? () #27 0x00000046 in ?? ()
This works fine for me here with fairly up-to-date KDE-CVS and qt. Which Version of KDE/Qt are you using?
I have been able to reproduce the problem on another computer (this time an AMD XP based machine) and I have also emerge'd the latest kdevelop 3 rc1 and also updated all the other packages on my machine and it still crashes in the same place. That is two of us with the same problem, and I have tried it out on both my itnel pentium 3 (mobile) based laptop and on my AMD XP based computer. I was hopeing that the rc1 update would of included a fix for it so that I could get coding.
I am currently using QT 3.2.3 and KDE 3.2 rc1. I was using KDE 3.2b2. I am using all the latest packages as I only just emerge'd last night. The only packages removed from the package.mask file so that they will be updated if necissary are the KDE ones.
The crash happens after the wizard has created all the files. If you attempt to open them with KDevelop (after reloading it) it crashes again. :-(
same problem here with 3.0.0 (unfortunately same non debug backtrace) using Qt 3.2.3r1 and KDE 3.2.0rc1 ... I am currently rebuilding Qt 3.3.0
you don't happen to have any other kdevelops (like from source) around do you? "which kdevelop" should show "/usr/bin/kdevelop"
After removing .kde3.2/share/config/kdeveloprc I can for open a Project. but only one. To open an other I must quit kdevelop an remove the file again.
I have only one copy of KDevelop and it dows report the location that you say.
I have now the same problem with kdevelop 3.0.0 stable release. The version before worked nicely. The only critical thing I changed was kde 3.1.5 to kde3.2.0 while doing the updgrade to kde 3.0.0. I have done some gcc and glibc updtaes as well, but recompiling kdevelop didn't solve it. Maybe recompiling qt helps?
I had the same problem, but now it seems have gone, I don't know why... Maybe because I upgraded valgrind from 2.0.0 to 2.1.0
I've been having the same problem with KDevelop, and I found what seems to be the solution on the KDE bug site. Take a look here: http://bugs.kde.org/show_bug.cgi?id=73346#c7 The patch looks like this: --- kdelibs-3.2.0/kmdi/kmdiguiclient.cpp 2004-01-17 07:53:20.000000000 -0500 +++ kdelibs-3.2.0new/kmdi/kmdiguiclient.cpp 2004-02-08 08:40:36.464098040 -0500 @@ -61,7 +61,7 @@ { if (m_dw) { connect(this,SIGNAL(toggled(bool)),this,SLOT(slotToggled(bool))); - connect(m_dw->dockManager(),SIGNAL(change()),this,SLOT(anDWChanged())); + //connect(m_dw->dockManager(),SIGNAL(change()),this,SLOT(anDWChanged())); //connect(m_dw,SIGNAL(destroyed()),this,SLOT(slotWidgetDestroyed())); setChecked(m_dw->mayBeHide()); } So, two things then, (1) Is it possible to have this patch added when the package is emerged, and (2) In the meantime, how would one go about applying this patch manually when emerging kdelib?
I have reinstalled my machine from scratch with all the latest gentoo packages and it seems to work ok now. I am going to do the same to my laptop and see if it gets fixed on that as well.
It seems that there's a problem with the patch applied by portage. See this http://forums.gentoo.org/viewtopic.php?t=132392&highlight=kdevelop and this http://bugs.kde.org/show_bug.cgi?id=73346#c7 Commenting the epatch line in the ebuild file should work.
should be fixed now with 3.0.1
