kdevelop 1.2 crashes at"debug(...)"
Mirko Leschikar
m.leschikar at web.de
Wed Jun 14 23:22:18 BST 2000
Hello,
> Mirko, please, compile it using the --enable-debug flag for make. Then
> start
> kdevelop within the debugger:
> gdb /opt/kde/bin/kdevelop
> Run kdevelop there and after the crash type:
> bt
> on the gdb command-line. That will print the backtrace that tells in which
> class
> and method kdevelop crashes.
> Send the backtrace output to us. Maybe we see more...
#0 0xe9 in ?? ()
#1 0x406477e6 in _IO_vfprintf (s=0x406f4c80, format=0x81fabc3
"CClassView::refresh( proj )", ap=0xbfffeae8)
at vfprintf.c:1018
#2 0x4013eeee in debug () from /usr/local/qt/lib/libqt.so.1
#3 0x80990df in CClassView::refresh (this=0x82a5c38, proj=0x83be378) at
cclassview.cpp:262
#4 0x808c71f in CKDevelop::refreshTrees (this=0x829ec48, iFileList=0x0) at
ckdevelop_noslot.cpp:558
#5 0x8069b3f in CKDevelop::slotViewRefresh (this=0x829ec48) at
ckdevelop.cpp:793
#6 0x8094f9b in CKDevelop::slotProjectNewAppl (this=0x829ec48) at
ckdevelop_project.cpp:703
#7 0x401192b3 in QObject::activate_signal () from
/usr/local/qt/lib/libqt.so.1
#8 0x4017cbf6 in QPopupMenu::mouseReleaseEvent () from
/usr/local/qt/lib/libqt.so.1
#9 0x4012e00a in QWidget::event () from /usr/local/qt/lib/libqt.so.1
#10 0x400f3f80 in QApplication::notify () from /usr/local/qt/lib/libqt.so.1
#11 0x401a32e3 in QETWidget::translateMouseEvent () from
/usr/local/qt/lib/libqt.so.1
#12 0x401a1259 in QApplication::x11ProcessEvent () from
/usr/local/qt/lib/libqt.so.1
#13 0x401a0da7 in QApplication::processNextEvent () from
/usr/local/qt/lib/libqt.so.1
#14 0x401a1c29 in QApplication::enter_loop () from
/usr/local/qt/lib/libqt.so.1
#15 0x401a0d25 in QApplication::exec () from /usr/local/qt/lib/libqt.so.1
#16 0x807af5e in main (argc=1, argv=0xbffff534) at main.cpp:61
I comppiled kdevelop again this morning and had a closer look at
compiler warnings, but there was nothing special. And I don´t think that my
Suse6.2 - System has any really obsolete libraries, which lead to the crash.
Is it possible that my previous installation of kdevelop 1.1 ( which I never
tested , shame on me) left some old files in the installation directories ?
Greetings
Mirko
--
Mirko Leschikar * EMail: m.leschikar at web.de
More information about the KDevelop
mailing list