Bug 111288 - KDevelop crashes on first startup. Second time works fine
Summary: KDevelop crashes on first startup. Second time works fine
Status: RESOLVED DUPLICATE of bug 69906
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-22 20:25 UTC by Linus McCabe
Modified: 2005-08-25 05:52 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 Linus McCabe 2005-08-22 20:25:24 UTC
Version:           SVN 3.5 branch (using KDE KDE 3.4.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

The first time I start KDevelop, it loads up and seems to be fine, but then it freezes and crashes with the backtrace below.

Second time I start KDevelop, it works just fine.

This happens every time after I've had my computer turned off.

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread 1076042944 (LWP 3789)]
[New Thread 1098644400 (LWP 3806)]
[KCrash handler]
#4  0x4a6d7d02 in QString::operator= () from /usr/lib/libqt-mt.so.3
#5  0x4aa13456 in KURL::operator= () from /usr/lib/libkdecore.so.4
#6  0x4aa0fa3f in KURL::KURL () from /usr/lib/libkdecore.so.4
#7  0x4b2464ce in KFileTreeBranch::parentKFTVItem () from /usr/lib/libkio.so.4
#8  0x4b2466a5 in KFileTreeBranch::addItems () from /usr/lib/libkio.so.4
#9  0x4b247a4d in KFileTreeBranch::qt_invoke () from /usr/lib/libkio.so.4
#10 0x4a403f9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#11 0x4b16616d in KDirLister::newItems () from /usr/lib/libkio.so.4
#12 0x4b1650fe in KDirLister::emitItems () from /usr/lib/libkio.so.4
#13 0x4b15f61b in KDirListerCache::slotEntries () from /usr/lib/libkio.so.4
#14 0x4b166e90 in KDirListerCache::qt_invoke () from /usr/lib/libkio.so.4
#15 0x4a403f9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#16 0x4b0ba174 in KIO::ListJob::entries () from /usr/lib/libkio.so.4
#17 0x4b0a8f02 in KIO::ListJob::slotListEntries () from /usr/lib/libkio.so.4
#18 0x4b0ba439 in KIO::ListJob::qt_invoke () from /usr/lib/libkio.so.4
#19 0x4a403f9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0x4b09567d in KIO::SlaveInterface::listEntries ()
   from /usr/lib/libkio.so.4
#21 0x4b09414b in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#22 0x4b0934f9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#23 0x4b090f2b in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#24 0x4b092c48 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#25 0x4a403f9c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#26 0x4a4040fd in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#27 0x4a743cd2 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#28 0x4a420780 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#29 0x4a3a769f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#30 0x4a3a6c9e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#31 0x4a97fa85 in KApplication::notify () from /usr/lib/libkdecore.so.4
#32 0x4a39709a in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#33 0x4a350533 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#34 0x4a3b9a58 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#35 0x4a3b9908 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#36 0x4a3a78f1 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#37 0x0804e4dd in main ()
Comment 1 Jens Dagerbo 2005-08-25 05:52:57 UTC
Dupe

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