Bug 82125 - crash c++ code completition pcs persistant store
Summary: crash c++ code completition pcs persistant store
Status: RESOLVED DUPLICATE of bug 74664
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.0.3
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-25 00:53 UTC by Weiland
Modified: 2004-05-26 22:55 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 Weiland 2004-05-25 00:53:19 UTC
Version:           3.0.3 (using KDE KDE 3.2.2)
Installed from:    SuSE RPMs
Compiler:          gcc, cpp 3.3.3 
OS:                Linux

Reproducing:
 - create a simple Qt hello application
 - in Project options -- C++ specific -- Code completition add a pcs for Qt/Kdelibs
 - Type "QApplic", and than <Ctrl-Space> (the code completition shortcut)

Side effect: When starting kdevelop again there is a window named "QApplication", that shows the html-source of the QApplication manpage

Versions:
kdevelop3-3.0.3-2
kdebase3-3.2.2-8
qt3-3.3.2-3

Trace:

(no debugging symbols found)...Using host libthread_db library "/lib/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)...[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 12884)]
[New Thread 32769 (LWP 12891)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 12884)]
[New Thread 32769 (LWP 12891)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 12884)]
[New Thread 32769 (LWP 12891)]
[New Thread 16386 (LWP 12892)]
0x417bc19b in waitpid () from /lib/libpthread.so.0
#0  0x417bc19b in waitpid () from /lib/libpthread.so.0
#1  0x40e091d8 in __JCR_LIST__ () from /opt/kde3/lib/libkdecore.so.4
#2  0x00000000 in ?? ()
#3  0x40d51bf2 in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#4  0x417bae31 in __pthread_sighandler () from /lib/libpthread.so.0
#5  <signal handler called>
#6  0x4215b1f8 in GCatalog<Tag>::query ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#7  0x4211b8d6 in CodeInformationRepository::query ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#8  0x421312b6 in CppCodeCompletion::computeCompletionEntryList ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#9  0x42137881 in CppCodeCompletion::completeText ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#10 0x42138fd8 in CppSupportPart::slotCompleteText ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#11 0x42149e22 in CppSupportPart::qt_invoke ()
   from /opt/kde3/lib/kde3/libkdevcppsupport.so
#12 0x4110d25e in QObject::activate_signal (this=0x8a6c330, clist=)
    at qconnection.h:56
#13 0x4110da06 in QObject::activate_signal (this=) at kernel/qobject.cpp:2325
#14 0x40a80639 in KAction::activated () from /opt/kde3/lib/libkdeui.so.4
#15 0x40a8065d in KAction::slotActivated () from /opt/kde3/lib/libkdeui.so.4
#16 0x40a88e51 in KAction::qt_invoke () from /opt/kde3/lib/libkdeui.so.4
#17 0x4110d25e in QObject::activate_signal (this=0x8998268, clist=)
    at qconnection.h:56
#18 0x4110da06 in QObject::activate_signal (this=) at kernel/qobject.cpp:2325
#19 0x40ccab69 in KAccelPrivate::menuItemActivated ()
   from /opt/kde3/lib/libkdecore.so.4
#20 0x40d72210 in KAccelPrivate::eventFilter ()
   from /opt/kde3/lib/libkdecore.so.4
#21 0x4110dafe in QObject::activate_filters (this=0x8210678, e=0xbfffef80)
    at kernel/qobject.cpp:902
#22 0x4110dbe0 in QObject::event (this=) at kernel/qobject.cpp:735
#23 0x411426df in QWidget::event (this=) at kernel/qwidget.cpp:4653
#23 0x411426df in QWidget::event (this=) at kernel/qwidget.cpp:4653
#24 0x41205e22 in QMainWindow::event (this=) at widgets/qmainwindow.cpp:1686
#25 0x404c7031 in KMdiMainFrm::event () from /opt/kde3/lib/libkmdi.so.1
#26 0x410abe3f in QApplication::internalNotify (this=0x0, receiver=0x8210678,
    e=) at qevent.h:144
#27 0x410add62 in QApplication::notify (this=0xbffff4c0, receiver=0x89df0d0,
    e=0xbfffef80) at kernel/qapplication.cpp:2377
#28 0x40d9a044 in KApplication::notify () from /opt/kde3/lib/libkdecore.so.4
#29 0x40d1868f in KAccelEventHandler::x11Event ()
   from /opt/kde3/lib/libkdecore.so.4
#30 0x40d93df2 in KApplication::x11EventFilter ()
   from /opt/kde3/lib/libkdecore.so.4
#31 0x41038e07 in qt_x11EventFilter (ev=) at kernel/qapplication_x11.cpp:382
#32 0x41049239 in QApplication::x11ProcessEvent (this=0xbffff4c0,
    event=0xbffff330) at kernel/qapplication_x11.cpp:3277
#33 0x4105a8b5 in QEventLoop::processEvents (this=0x81db040, flags=4)
    at kernel/qeventloop_x11.cpp:192
#34 0x410c3881 in QEventLoop::enterLoop (this=) at kernel/qeventloop.cpp:198
#35 0x410c36c6 in QEventLoop::exec (this=0x81db040)
    at kernel/qeventloop.cpp:145
#36 0x410ad72f in QApplication::exec (this=0xbffff4c0)
    at kernel/qapplication.cpp:2743
#37 0x0808a3a6 in main ()
Comment 1 Jens Dagerbo 2004-05-25 21:57:54 UTC
Dupe.

What Berkeley DB version are you using? 4.2.x is known to crash KDevelop, but some reports suggest any KDE app that uses bdb on SuSE (9.1) bombs.

*** This bug has been marked as a duplicate of 74664 ***
Comment 2 Weiland 2004-05-26 01:06:32 UTC
> http://bugs.kde.org/show_bug.cgi?id=82125  
>
> What Berkeley DB version are you using? 4.2.x is known to crash 
> KDevelop, but some reports suggest any KDE app that uses bdb on SuSE 
> (9.1) bombs.

berkeley db 4.2.52

p.s. Im sorry for not finding the similar report.

Weiland

_____________________________________________________________
ueberschuss.de - be source, not result
Free Email & mehr: http://www.ueberschuss.de

Comment 3 Weiland 2004-05-26 02:28:43 UTC
>> What Berkeley DB version are you using? 4.2.x is known 
>> to crash KDevelop, but some reports suggest any KDE app 
>> that uses bdb on SuSE (9.1) bombs.
>
> berkeley db 4.2.52

downgraded to db-4.1.25-76 (ignoring some rpm-package dependencies)
removed all *.pcs files from kdevelop projects
created new pcs for kdelibs
kdevelop still crashes on completition


_____________________________________________________________
ueberschuss.de - be source, not result
Free Email & mehr: http://www.ueberschuss.de

Comment 4 Amilcar do Carmo Lucas 2004-05-26 13:41:18 UTC
You should not ignore packages dependencies.

You should compile it from source. It gives you the best results.

I use SuSE 9.1 too and here it does not seam to bomb :)
Comment 5 Sandy Meier 2004-05-26 22:55:18 UTC
I compiled it with the 
"--with-db-libdir=/usr/lib --with-db-includedir=/usr/include/db41 
--with-db-lib=db-4.1"

as you suggested. And removed "~/.kde/share/apps/kdevcppsupport/pcs"

But it still crashed :-(

libkdevcatalog seems to be correctly linked.


smeier@linux:/opt/kde3/lib> ldd libkdevcatalog.so
        linux-gate.so.1 =>  (0xffffe000)
        libdb-4.1.so => /usr/lib/libdb-4.1.so (0x4001a000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x400d9000)
        libm.so.6 => /lib/tls/libm.so.6 (0x40195000)
        libc.so.6 => /lib/tls/libc.so.6 (0x401b8000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x402cd000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)