Bug#31794: intermittent won't save then crash on close all

abatters at widomaker.com abatters at widomaker.com
Wed Aug 29 17:14:39 UTC 2001

Package: kdevelop
Version: 2.0 (using KDE 2.2.0 )
Severity: normal
Installed from:    RedHat RPMs
Compiler:          gcc 2.96
OS:                Linux
OS/Compiler notes: RedHat 7.1 with custom-compiled 2.4.9 kernel

I am using the editor part of KDevelop for editing console C programs; I compile, run, and debug using a separate console.  I just upgraded from version 1.4 to version 2.0.  With version 2.0, sometimes when I press Ctrl+S to save the file, KDevelop does not actually save it (I can tell by looking at the file in vi and comparing to what the KDevelop window shows).  Pressing Ctrl+S again results in the same thing.  When this happens, the File->Save menu item is greyed out.  Clicking on the Save As menu item does not bring up any dialog box.  I even tried to highlight all of the text and copy it into a different application (to avoid losing my changes), but the copy operation didn't work either (it just pasted something that I had copied a bit earlier).  Selecting File->Close All causes the dialog box to pop up asking if the modified document should be saved; but clicking Yes causes KDevelop to crash.  Here is the backtrace of that crash:

(no debugging symbols found)...0x411e24b9 in __wait4 () from /lib/libc.so.6
#0  0x411e24b9 in __wait4 () from /lib/libc.so.6
#1  0x4125d6e0 in __DTOR_END__ () from /lib/libc.so.6
#2  0x409bbeb8 in KCrash::defaultCrashHandler () at eval.c:41
#3  <signal handler called>
#4  0x0806d94e in CToolClass::writeToolConfig () at eval.c:41
#5  0x080a17e1 in CToolClass::writeToolConfig () at eval.c:41
#6  0x080705e6 in CToolClass::writeToolConfig () at eval.c:41
#7  0x0807acd7 in CToolClass::writeToolConfig () at eval.c:41
#8  0x40caca81 in QObject::activate_signal ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#9  0x40cdd932 in QSignal::activate () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#10 0x40d7c359 in QPopupMenu::mouseReleaseEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#11 0x40cf3d71 in QWidget::event () from /usr/lib/qt-2.3.1/lib/libqt.so.2

#12 0x40c5c6b1 in QApplication::notify () from /usr/lib/qt-2.3.1/lib/libqt.so.2

#13 0x40923cc9 in KApplication::notify () at eval.c:41
#14 0x40c2a974 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#15 0x40c28068 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#16 0x40c2703a in QApplication::processNextEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#17 0x40c5e56c in QApplication::enter_loop ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#18 0x40c26fb7 in QApplication::exec () from /usr/lib/qt-2.3.1/lib/libqt.so.2
#19 0x080eb052 in CToolClass::writeToolConfig () at eval.c:41
#20 0x4114b2ae in __libc_start_main (

    main=0x80ea0f0 <CToolClass::writeToolConfig(QValueList<CToolApp> const &)+526464>, argc=1, ubp_av=0xbffffd44, init=0x80621a4 <_init>, 

    fini=0x81fd0b0 <_fini>, rtld_fini=0x4000cf28 <_dl_fini>, 
    stack_end=0xbffffd3c) at ../sysdeps/generic/libc-start.c:129

None of these problems show up when I first start KDevelop.  It behaves correctly for a while and then breaks.  I have not yet determined exactly what triggers the problem.

I noticed that bug #31390 involves a crash on Close All, but due to lack of additional details I wasn't sure if this is a duplicate or not.

(Submitted via bugs.kde.org)

to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«

More information about the KDevelop-devel mailing list