Bug 87558 - crash when use auto completion
Summary: crash when use auto completion
Status: RESOLVED DUPLICATE of bug 74664
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.0.4
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-20 02:23 UTC by Rinat Zakirov
Modified: 2004-11-18 20:08 UTC (History)
1 user (show)

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


Attachments
Output from gdb (5.56 KB, text/plain)
2004-11-18 19:51 UTC, Krzysztof Lichota
Details
Kdevelop project file (1.86 KB, text/plain)
2004-11-18 19:52 UTC, Krzysztof Lichota
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rinat Zakirov 2004-08-20 02:23:07 UTC
Version:           3.0.4 (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs
Compiler:          gcc 3.3 20040412 
OS:                Linux

In any case when I use auto completion it crahes.
for example i type sprintf( and when I type "(" it suddenly crashes.
At "classname::" as I type the second ":" it crashes.

In Settings->Configure Kdevelop->Plugins nothing is selected, all plugins are off.

I have seen autocompletion working on 
#include "...  it worked here fine.

But in any other place I remember it crahed.

Not sure if this would be useful:

(no debugging symbols found)...Using host libthread_db library "/lib/tls/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)...[Thread debugging using libthread_db enabled]
[New Thread -150512736 (LWP 13696)]
[New Thread -156705872 (LWP 13698)]
[Thread debugging using libthread_db enabled]
[New Thread -150512736 (LWP 13696)]
[New Thread -156705872 (LWP 13698)]
[Thread debugging using libthread_db enabled]
[New Thread -150512736 (LWP 13696)]
[New Thread -156705872 (LWP 13698)]
(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)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0x00934402 in ?? ()
#0  0x00934402 in ?? ()
#1  0x4f5a8eab in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#2  0x41c1ab60 in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
#3  <signal handler called>
#4  0x0030a5ec in GCatalog<Tag>::query ()
   from /usr/lib/kde3/libkdevcppsupport.so
#5  0x00307a73 in CodeInformationRepository::query ()
   from /usr/lib/kde3/libkdevcppsupport.so
#6  0x002eda81 in CppCodeCompletion::computeSignatureList ()
   from /usr/lib/kde3/libkdevcppsupport.so
#7  0x002e43b3 in CppCodeCompletion::completeText ()
   from /usr/lib/kde3/libkdevcppsupport.so
#8  0x002e0c56 in CppCodeCompletion::slotTimeout ()
   from /usr/lib/kde3/libkdevcppsupport.so
#9  0x002f0bd5 in CppCodeCompletion::qt_invoke ()
   from /usr/lib/kde3/libkdevcppsupport.so
#10 0x41615a7c in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x416158a4 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#12 0x41953b8b in QTimer::timeout () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#13 0x41637182 in QTimer::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x415b99ff in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x415b8ffe in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x41b86229 in KApplication::notify () from /usr/lib/libkdecore.so.4
#17 0x415a9355 in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x415646db in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x415cbbf8 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x415cbaa8 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x415b9c51 in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x08062548 in main ()
Comment 1 Rinat Zakirov 2004-08-20 02:30:19 UTC
BTW, I have Fedora Core 2 and I installed KDE from standard RPMs that are included in there. 
Comment 2 Rinat Zakirov 2004-08-20 05:21:39 UTC
I had 4.2 Berkeley DB. I took 3.3 and installed it. I keep crashing on 3.1.0 too.
Comment 3 Rinat Zakirov 2004-08-20 05:27:01 UTC
And now after installing 3.3 Berkeley DB and compiling and installing 3.1.0 KDev it crashes while setting up the new PCS for my includes.
Comment 4 Rinat Zakirov 2004-08-20 06:24:25 UTC
kdevelop crashes while it makes persistent class storage for boost(www.boost.org) libraries
Comment 5 Krzysztof Lichota 2004-11-18 19:48:04 UTC
I have similar problem with Kdevelop 3.0.2 (KDE 3.3.0) from Suse RPMs (for Suse 9.1). 

Here are the exact steps to reproduce it:
1. Checkout sources of kdelibs, tag KDE_3_3_1_RELEASE.
2. Create project using import project, choose "C++ application, custom makefiles" (don't know if it affects), choose only kdelibs/kdecore directory to import.
3. Choose "populate project with files under directory".
4. When it finishes updating, go to KApplication::init() method, type "this->" and wait for completion - then it crashes.

I will attach the project file and log from gdb (unfortunately without symbols). There is some assertion printed in gdb output.
Comment 6 Krzysztof Lichota 2004-11-18 19:51:14 UTC
Created attachment 8326 [details]
Output from gdb

Output from gdb. Run kdevelop with described scenario to cause crash.
Comment 7 Krzysztof Lichota 2004-11-18 19:52:56 UTC
Created attachment 8327 [details]
Kdevelop project file
Comment 8 Jens Dagerbo 2004-11-18 20:03:27 UTC
Krzysztof, 

Update to KDevelop-3.1.x. If you are using 3.0.x on SuSE you are most likely getting bdb-4.2.x and that WILL crash!
Comment 9 Jens Dagerbo 2004-11-18 20:08:10 UTC
This whole report is a dupe, btw.

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