Bug 120855 - KDevelop crashes after loading project - but only for the first time
Summary: KDevelop crashes after loading project - but only for the first time
Status: RESOLVED DUPLICATE of bug 69906
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-27 10:37 UTC by Sasa Kara
Modified: 2006-04-18 23:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
gdb backtrace plus output of a few more gdb commands (4.28 KB, text/plain)
2006-02-22 18:14 UTC, Tobi Vollebregt
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Sasa Kara 2006-01-27 10:37:39 UTC
Version:           3.3 (using KDE KDE 3.5.0)
Installed from:    SuSE RPMs
Compiler:          Installed from precompiled binaries 
OS:                Linux

When I start the computer and run KDevelop for the first time, it always crashes (well, I recall that it didn't crash a couple of times, but that was long time ago and it was a different version - 3.2.??). After that I start KDevelop a second time and it never crashes.
I have KDE 3.5 and KDevelop 3.3 (and SuSE 10.0), but it was happening before with earlier versions. I open KDevelop with the same project all the time, so it might be a problem with the project.
Recently, subversion integration stopped working (after upgrading to KDE 3.5). Maybe it is connected with the bug 110222...

It is not that annoying as it always starts for the second time, but I would be happy to assist and provide any additional information.

This is the backtrace (with '(no debugging symbols found)' omitted:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 1105093440 (LWP 7415)]
[New Thread 1120988080 (LWP 7416)]
[Thread debugging using libthread_db enabled]
[New Thread 1105093440 (LWP 7415)]
[New Thread 1120988080 (LWP 7416)]
[Thread debugging using libthread_db enabled]
[New Thread 1105093440 (LWP 7415)]
[New Thread 1120988080 (LWP 7416)]
[KCrash handler]
#7  0x40edf682 in QString::operator= () from /usr/lib/qt3/lib/libqt-mt.so.3
#8  0x407dbee6 in KURL::operator= () from /opt/kde3/lib/libkdecore.so.4
#9  0x40824d2f in KURL::KURL () from /opt/kde3/lib/libkdecore.so.4
#10 0x40374dbb in KFileTreeBranch::parentKFTVItem ()
   from /opt/kde3/lib/libkio.so.4
#11 0x403aa2ef in KFileTreeBranch::addItems () from /opt/kde3/lib/libkio.so.4
#12 0x403aadcd in KFileTreeBranch::qt_invoke () from /opt/kde3/lib/libkio.so.4
#13 0x40c05a49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#14 0x402b2d85 in KDirLister::newItems () from /opt/kde3/lib/libkio.so.4
#15 0x402b310b in KDirLister::emitItems () from /opt/kde3/lib/libkio.so.4
#16 0x4031afd3 in KDirListerCache::slotUpdateResult ()
   from /opt/kde3/lib/libkio.so.4
#17 0x4031b95e in KDirListerCache::qt_invoke () from /opt/kde3/lib/libkio.so.4
#18 0x40c05a49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#19 0x4022b212 in KIO::Job::result () from /opt/kde3/lib/libkio.so.4
#20 0x4027f1dc in KIO::Job::emitResult () from /opt/kde3/lib/libkio.so.4
#21 0x4027f34e in KIO::SimpleJob::slotFinished ()
   from /opt/kde3/lib/libkio.so.4
#22 0x4027f6dd in KIO::ListJob::slotFinished () from /opt/kde3/lib/libkio.so.4
#23 0x402949be in KIO::ListJob::qt_invoke () from /opt/kde3/lib/libkio.so.4
#24 0x40c05a49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40c05ef0 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x40225e6c in KIO::SlaveInterface::finished ()
   from /opt/kde3/lib/libkio.so.4
#27 0x4029975c in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#28 0x4023e6f7 in KIO::SlaveInterface::dispatch ()
   from /opt/kde3/lib/libkio.so.4
#29 0x402432ab in KIO::Slave::gotInput () from /opt/kde3/lib/libkio.so.4
#30 0x4024345b in KIO::Slave::qt_invoke () from /opt/kde3/lib/libkio.so.4
#31 0x40c05a49 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x40c06021 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x40f48490 in QSocketNotifier::activated ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0x40c24b30 in QSocketNotifier::event ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x40ba5d41 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x40ba66b9 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0x408abeee in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#38 0x40b99bcd in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0x40b53f03 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0x40bbcc39 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0x40bbcb36 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#42 0x40ba568f in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0x0804e376 in ?? ()
#44 0xbfcf8520 in ?? ()
#45 0x080e0cf0 in ?? ()
#46 0xbfcf869c in ?? ()
#47 0x00000001 in ?? ()
#48 0x0805221b in vtable for QGList ()
#49 0x00000001 in ?? ()
#50 0x08052310 in vtable for QGList ()
#51 0x080522bf in vtable for QGList ()
#52 0x08051af9 in vtable for QGList ()
#53 0x08051ae5 in vtable for QGList ()
#54 0x00000000 in ?? ()
#55 0xbfcf8560 in ?? ()
#56 0x40007ec4 in do_lookup_x () from /lib/ld-linux.so.2
#57 0x4116eea0 in __libc_start_main () from /lib/tls/libc.so.6
#58 0x0804d801 in ?? ()
Comment 1 Tobi Vollebregt 2006-02-22 18:10:27 UTC
Looking at the backtrace I suppose I got the same bug, only in my case it happens quite often I open kdevelop3 with the project I'm working on, unless I delete the .filelist and .pcs and repopulate the project with all files below project directory (never experienced a crash in that case, but that could be random).

I installed it via the binary packages in Kubuntu (dapper drake). It is version 3.3.1 in KDE 3.5.1.

I will attach a backtrace plus some commands run in gdb which suggest the crash results from a read from uninitialized memory or overwriting a pointer. Anyway, it segfaults while trying to read from a dangling QStringData* d (in QString).

It worked fine when I ran it in valgrind --tool=memcheck.
Comment 2 Tobi Vollebregt 2006-02-22 18:14:18 UTC
Created attachment 14815 [details]
gdb backtrace plus output of a few more gdb commands
Comment 3 Jens Dagerbo 2006-04-18 23:54:42 UTC
Dupe

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