Bug 57571 - crash on calling code completion
Summary: crash on calling code completion
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-22 21:03 UTC by jalal
Modified: 2003-05-09 14:01 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jalal 2003-04-22 21:03:26 UTC
Version:           Gideon from CVS 22/04/03 (using KDE KDE 3.1.1a)
Installed from:    SuSE RPMs
Compiler:          gcc 2.95.3 
OS:          Linux

On entering a pointer:
m_pMyObj->

application crashes.
Repeatable.

[New Thread 1024 (LWP 12259)]
[New Thread 2049 (LWP 12261)]
[New Thread 1026 (LWP 12262)]
0x412c7099 in wait4 () from /lib/libc.so.6
#0  0x412c7099 in wait4 () from /lib/libc.so.6
#1  0x41341bd8 in __DTOR_END__ () from /lib/libc.so.6
#2  0x4117b072 in waitpid () from /lib/libpthread.so.0
#3  0x4094183e in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x41178a74 in pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x4124dab1 in kill () from /lib/libc.so.6
#7  0x41178982 in pthread_kill () from /lib/libpthread.so.0
#8  0x41178e6d in raise () from /lib/libpthread.so.0
#9  0x4124eedb in abort () from /lib/libc.so.6
#10 0x411a2a0b in FAMDebugLevel () from /usr/lib/libfam.so.0
#11 0x411a2a2c in FAMDebugLevel () from /usr/lib/libfam.so.0
#12 0x411a34a4 in FAMDebugLevel () from /usr/lib/libfam.so.0
#13 0x411a365c in FAMDebugLevel () from /usr/lib/libfam.so.0
#14 0x411a50da in FAMDebugLevel () from /usr/lib/libfam.so.0
#15 0x40e83a9e in QString::setLength () from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x40e8af53 in operator>> () from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0x46395736 in Tag::load () from /opt/kde3/lib/libkdevcatalog.so.0
#18 0x46395281 in Catalog::query () from /opt/kde3/lib/libkdevcatalog.so.0
#19 0x4635dfb1 in CodeInformationRepository::query ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#20 0x4635f384 in CodeInformationRepository::getTagsInScope ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#21 0x4635ffde in CodeInformationRepository::getEntriesInScope ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#22 0x4633cd32 in CppCodeCompletion::findAllEntries ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#23 0x4633ba3f in CppCodeCompletion::findAllEntries ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#24 0x4633a3cb in CppCodeCompletion::completeText ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#25 0x463350a9 in CppCodeCompletion::slotTimeout ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#26 0x4634195e in CppCodeCompletion::qt_invoke ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#27 0x40c7b3c4 in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x40c7b2fe in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40ed8249 in QTimer::timeout () from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x40c95c4f in QTimer::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x40c3009a in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x40c2fea7 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x408dfd5b in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#34 0x40c13ed5 in QEventLoop::activateTimers ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0x40bf64dd in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0x40c40520 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0x40c40467 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#38 0x40c30216 in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0x080669a9 in main ()
#40 0x4123c9ed in __libc_start_main () from /lib/libc.so.6
Comment 1 Thomas Wilczek 2003-04-22 21:27:32 UTC
Yep, I think I can reproduce this bug, too.(self compiled CVS gcc 3.2 SuSE 8.1) It happens 
when typing a new method declaration like: void foobar(const |<<<CRASH, well not crash but a 
total freeze up without any further repaint etc. 
 
cmd line output: 
... 
kdevelop (cpp support): CppCodeCompletion::completeText() 
kdevelop (cpp support): ch = ( 
kdevelop (cpp support): ch2 = t( 
kdevelop (cpp support): c = t 
kdevelop (cpp support): ------------------- AST FOUND -------------------- 
kdevelop (cpp support): ProblemReporter::reparse() 
 
Comment 2 jalal 2003-05-09 14:01:54 UTC
Fixed