Crash in 3.5 branch
Paulo Moura Guedes
moura at kdewebdev.org
Thu Nov 3 00:31:03 UTC 2005
Hi,
KDevelop is crashing a lot when I start it. The only way I can use it, when it
starts crashing is to pass a project on the command line, even if it is the
same.
The backtrace I'm getting is the following:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1108372320 (LWP 7634)]
[New Thread 1124305840 (LWP 7637)]
[Thread debugging using libthread_db enabled]
[New Thread 1108372320 (LWP 7634)]
[New Thread 1124305840 (LWP 7637)]
[Thread debugging using libthread_db enabled]
[New Thread 1108372320 (LWP 7634)]
[New Thread 1124305840 (LWP 7637)]
[KCrash handler]
#3 0x41ae6882 in QString::operator= () from /usr/lib/qt3/lib/libqt-mt.so.3
#4 0x413ba06f in KURL::operator= (this=0xbfffdc90, _u=@0x8d855e0)
at kurl.cpp:1062
#5 0x413b685d in KURL (this=0xbfffdc90, _u=@0x8d855e0) at kurl.cpp:478
#6 0x40e80338 in KFileTreeBranch::parentKFTVItem (this=0x8d372f0,
item=0x8d855d8) at kfiletreebranch.cpp:123
#7 0x40e8063a in KFileTreeBranch::addItems (this=0x8d372f0, list=@0x8d7fa68)
at kfiletreebranch.cpp:163
#8 0x40e82270 in KFileTreeBranch::qt_invoke (this=0x8d372f0, _id=12,
_o=0xbfffded0) at kfiletreebranch.moc:210
#9 0x417ff31e in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#10 0x40dadd53 in KDirLister::newItems (this=0x8d372f0, t0=@0x8d7fa68)
at kdirlister.moc:312
#11 0x40dacbe7 in KDirLister::emitItems (this=0x8d372f0) at
kdirlister.cpp:2284
#12 0x40da6ba1 in KDirListerCache::slotEntries (this=0x8603a58, job=0x86b3ac0,
entries=@0xbfffe420) at kdirlister.cpp:958
#13 0x40daef6c in KDirListerCache::qt_invoke (this=0x8603a58, _id=6,
_o=0xbfffe0d0) at kdirlister_p.moc:131
#14 0x417ff31e in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40d0baba in KIO::ListJob::entries (this=0x86b3ac0, t0=0x86b3ac0,
t1=@0xbfffe420) at jobclasses.moc:1699
#16 0x40cfb721 in KIO::ListJob::slotListEntries (this=0x86b3ac0,
list=@0xbfffe420) at job.cpp:2006
#17 0x40d0be31 in KIO::ListJob::qt_invoke (this=0x86b3ac0, _id=19,
_o=0xbfffe2e0) at jobclasses.moc:1737
#18 0x417ff31e in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x40ce6019 in KIO::SlaveInterface::listEntries (this=0x8b1b8e0,
t0=@0xbfffe420) at slaveinterface.moc:255
#20 0x40ce4414 in KIO::SlaveInterface::dispatch (this=0x8b1b8e0, _cmd=106,
rawdata=@0xbfffe4b0) at slaveinterface.cpp:263
#21 0x40ce3f64 in KIO::SlaveInterface::dispatch (this=0x8b1b8e0)
at slaveinterface.cpp:173
#22 0x40ce19d1 in KIO::Slave::gotInput (this=0x8b1b8e0) at slave.cpp:300
#23 0x40ce344f in KIO::Slave::qt_invoke (this=0x8b1b8e0, _id=4, _o=0xbfffe5f0)
at slave.moc:113
#24 0x417ff31e in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x417ff94d in QObject::activate_signal ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x41b51f30 in QSocketNotifier::activated ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#27 0x4181ef90 in QSocketNotifier::event ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x4179cbaf in QApplication::internalNotify ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x4179e773 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x4131f1d0 in KApplication::notify (this=0xbfffec70, receiver=0x86190f8,
event=0xbfffe970) at kapplication.cpp:550
#31 0x41790d26 in QEventLoop::activateSocketNotifiers ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x4174a112 in QEventLoop::processEvents ()
from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x417b4b41 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0x417b4986 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x4179e63f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x0804f3ba in main (argc=2, argv=0xbfffee24)
at /home/moura/kdesvn-3.5/kdevelop/src/main.cpp:145
Is this a known issue?
Paulo
More information about the KDevelop-devel
mailing list