[Bug 76322] New: kdevelop (IDEAl mode) crashes by (multiple) rmb clicks on tab (crash, bt?)

Marco Krohn marco.krohn at gmx.de
Sat Feb 28 00:23:07 UTC 2004

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
           Summary: kdevelop (IDEAl mode) crashes by (multiple) rmb clicks
                    on tab (crash, bt?)
           Product: kdevelop
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel kdevelop org
        ReportedBy: marco.krohn gmx de

Version:           3.0.90-CVS (using KDE 3.2.90 (CVS >= 20040117), compiled sources)
Compiler:          gcc version 3.3.3 20040125 (prerelease) (Debian)
OS:          Linux (i686) release 2.4.23-1-k7

The following is a strange one, but crashes kdevelop reproducable for me:

1. load any project (I have tested php, c++) with at least two tabs (using IDEAl mode)
2. click multiple times with the right mouse button on one of the tabs (left or right tab, active or non-active is not important). Do that fast and slowly move the mouse around (still over the tab) and move it over the close-button

KDevelop than crashes for me with the following bt:

[New Thread 16384 (LWP 2503)]
0x41a63bd8 in waitpid () from /lib/libpthread.so.0
#0  0x41a63bd8 in waitpid () from /lib/libpthread.so.0
#1  0x41004e98 in __JCR_LIST__ () from /opt/kde-new/lib/libkdecore.so.4
#2  0x41a62815 in __pthread_sighandler () from /lib/libpthread.so.0
#3  0x41bc64a8 in __libc_sigaction () from /lib/libc.so.6
#4  0x41316aab in QApplication::notify(QObject*, QEvent*) ()
   from /opt/qt-new/lib/libqt-mt.so.3
#5  0x40eccdfc in KApplication::notify(QObject*, QEvent*) (this=0xbffffa40, 
    receiver=0x8654a10, event=0xbffff5c0) at kapplication.cpp:506
#6  0x41318d75 in qt_dispatchEnterLeave(QWidget*, QWidget*) ()
   from /opt/qt-new/lib/libqt-mt.so.3
#7  0x412ad4ea in QApplication::x11ProcessEvent(_XEvent*) ()
   from /opt/qt-new/lib/libqt-mt.so.3
#8  0x412c35b1 in QEventLoop::processEvents(unsigned) ()
   from /opt/qt-new/lib/libqt-mt.so.3
#9  0x41329658 in QEventLoop::enterLoop() () from /opt/qt-new/lib/libqt-mt.so.3
#10 0x41329508 in QEventLoop::exec() () from /opt/qt-new/lib/libqt-mt.so.3
#11 0x413176f1 in QApplication::exec() () from /opt/qt-new/lib/libqt-mt.so.3
#12 0x08066b9b in main (argc=1, argv=0xbffffbb4) at main.cpp:128

I am afraid it's not too useful--perhaps a Qt bug? Qt unfortunately is compiled without debug info.

Testing the same thing with konqueror does not crash konqueror. While trying to reproduce that I sometimes only had to click 2-3 times, sometimes up to 20 times, but every time kdevelop crashed. Also I am quite sure that I have seen for a very short time a context menue showing up exactly when the crash happened (looking like one of these you get in konqueror). Strange...

More information about the KDevelop-devel mailing list