Bug 139556 - kdevelop rashes after project is loaded
Summary: kdevelop rashes after project is loaded
Status: RESOLVED DUPLICATE of bug 111900
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-03 13:40 UTC by Johannes Wienke
Modified: 2007-01-03 14:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Johannes Wienke 2007-01-03 13:40:57 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Gentoo Packages

Kdevelop crashes on startup, after a recent C++/Qt project is successfully loaded.

Backtrace:

(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1240061760 (LWP 32566)]
[New Thread -1252762720 (LWP 32579)]
[KCrash handler]
#9  0xb6bb5922 in QString::operator= () from /usr/qt/3/lib/libqt-mt.so.3
#10 0xb6f702f6 in KURL::operator= () from /usr/kde/3.5/lib/libkdecore.so.4
#11 0xb6f709a3 in KURL::KURL () from /usr/kde/3.5/lib/libkdecore.so.4
#12 0xb763088b in KFileTreeBranch::parentKFTVItem ()
   from /usr/kde/3.5/lib/libkio.so.4
#13 0xb763197a in KFileTreeBranch::addItems ()
   from /usr/kde/3.5/lib/libkio.so.4
#14 0xb7631ecd in KFileTreeBranch::qt_invoke ()
   from /usr/kde/3.5/lib/libkio.so.4
#15 0xb68e3859 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#16 0xb754f5d1 in KDirLister::newItems () from /usr/kde/3.5/lib/libkio.so.4
#17 0xb754f65b in KDirLister::emitItems () from /usr/kde/3.5/lib/libkio.so.4
#18 0xb755050b in KDirListerCache::slotEntries ()
   from /usr/kde/3.5/lib/libkio.so.4
#19 0xb755902a in KDirListerCache::qt_invoke ()
   from /usr/kde/3.5/lib/libkio.so.4
#20 0xb68e3859 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#21 0xb748e46e in KIO::ListJob::entries () from /usr/kde/3.5/lib/libkio.so.4
#22 0xb749fd5b in KIO::ListJob::slotListEntries ()
   from /usr/kde/3.5/lib/libkio.so.4
#23 0xb74a0040 in KIO::ListJob::qt_invoke () from /usr/kde/3.5/lib/libkio.so.4
#24 0xb68e3859 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#25 0xb747fc71 in KIO::SlaveInterface::listEntries ()
   from /usr/kde/3.5/lib/libkio.so.4
#26 0xb7481915 in KIO::SlaveInterface::dispatch ()
   from /usr/kde/3.5/lib/libkio.so.4
#27 0xb747ff68 in KIO::SlaveInterface::dispatch ()
   from /usr/kde/3.5/lib/libkio.so.4
#28 0xb747cc0b in KIO::Slave::gotInput () from /usr/kde/3.5/lib/libkio.so.4
#29 0xb747cdc0 in KIO::Slave::qt_invoke () from /usr/kde/3.5/lib/libkio.so.4
#30 0xb68e3859 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#31 0xb68e43a2 in QObject::activate_signal () from /usr/qt/3/lib/libqt-mt.so.3
#32 0xb6c1d1b0 in QSocketNotifier::activated ()
   from /usr/qt/3/lib/libqt-mt.so.3
#33 0xb6901950 in QSocketNotifier::event () from /usr/qt/3/lib/libqt-mt.so.3
#34 0xb6884687 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#35 0xb6885241 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#36 0xb6edd6ee in KApplication::notify ()
   from /usr/kde/3.5/lib/libkdecore.so.4
#37 0xb68792f1 in QEventLoop::activateSocketNotifiers ()
   from /usr/qt/3/lib/libqt-mt.so.3
#38 0xb683476e in QEventLoop::processEvents ()
   from /usr/qt/3/lib/libqt-mt.so.3
#39 0xb689b1b1 in QEventLoop::enterLoop () from /usr/qt/3/lib/libqt-mt.so.3
#40 0xb689b036 in QEventLoop::exec () from /usr/qt/3/lib/libqt-mt.so.3
#41 0xb688410f in QApplication::exec () from /usr/qt/3/lib/libqt-mt.so.3
#42 0x0804e1a4 in ?? ()
#43 0xbfede0cc in ?? ()
#44 0x080d6538 in ?? ()
#45 0xbfede248 in ?? ()
#46 0x00000001 in ?? ()
#47 0x08052420 in _IO_stdin_used ()
#48 0x00000001 in ?? ()
#49 0x0805250c in _IO_stdin_used ()
#50 0x080524c4 in _IO_stdin_used ()
#51 0x08051cfc in _IO_stdin_used ()
#52 0x08051ce8 in _IO_stdin_used ()
#53 0x0804bca8 in ?? ()
#54 0xb62e8070 in ?? ()
   from /usr/lib/gcc/i686-pc-linux-gnu/4.1.1/libstdc++.so.6
#55 0xb6282560 in __after_morecore_hook () from /lib/libc.so.6
#56 0x08062db8 in ?? ()
#57 0x03df6174 in ?? ()
#58 0xb704fdc8 in vtable for KApplication ()
   from /usr/kde/3.5/lib/libkdecore.so.4
#59 0x09691f60 in ?? ()
#60 0x080bc318 in ?? ()
#61 0x00000000 in ?? ()
Comment 1 Jens Dagerbo 2007-01-03 13:46:06 UTC
What KDevelop version are you running? Please update to KDevelop-3.4 RC2 and see if you can reproduce it.

This is an old familiar problem, that I think we've closed in 3.4. 
Comment 2 Johannes Wienke 2007-01-03 13:51:38 UTC
Well, 3.3.5 is declared as the stable version of kdevelop and actually there are only hard-masked gentoo ebuild for 3.4. Isn't that a a problem which should be solved in the stable version?
Comment 3 Jens Dagerbo 2007-01-03 14:07:54 UTC
I think I confused it with another bug...

Are you using the SVN plugin? The backtrace looks like it could be bug #111900.
Comment 4 Johannes Wienke 2007-01-03 14:11:00 UTC
Yes, I recently emerged kdevelop with subversion support. You can test this on you own. It's the kopete kdevelop project that's making the trouble:
http://kopete.kde.org/svnaccess.php
Comment 5 Jens Dagerbo 2007-01-03 14:17:52 UTC
Well.. the interesting thing is if the particular project that crashes loads the subversion plugin. 

If you can load the project without crashing, look in Project -> Project Options -> Version Control. Does it say subversion?

If not, look in the .kdevelop file for this line: <versioncontrol>kdevsubversion</versioncontrol> (and remove it to get away from the crash).
Comment 6 Johannes Wienke 2007-01-03 14:23:26 UTC
Yes, the project loads subversion (which isn't very striking, as it is an svn-project ;) an therefore it would be good to have svn-access). To get rid of that bug I can also close the project before I  quit kdevelop or delete thar last project file from kdeveloprc.
Comment 7 Jens Dagerbo 2007-01-03 14:32:33 UTC
Ok, then we have another dupe. Thanks for testing. :)

I'm afraid we're no closer to figuring out why this happens. It's something truly weird that happens when the subversion plugin interacts with the FileTree. :(

*** This bug has been marked as a duplicate of 111900 ***