Bug 71703

Summary:	QtEditor with non-default tabs crashes and other problems
Product:	[Applications] kdevelop	Reporter:	John A. Sullivan III <john.sullivan>
Component:	general	Assignee:	KDevelop Developers <kdevelop-devel>
Status:	RESOLVED DUPLICATE
Severity:	crash
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	RedHat Enterprise Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description John A. Sullivan III 2004-01-02 23:55:09 UTC

Version: (using KDE KDE 3.1)
Installed from: RedHat RPMs
Compiler: gcc 3.2.2-5
OS: Linux

I like to set my tabs to 4 spaces instead of the default 8. Doing this produces several problems and one regularly reproducible crash.

If I:
1) use the find function
2) successfully find some text
3) delete that multi-line text without closing the find next dialog
4) then click on yes (to the find next question)
the system reliably crashes. It did once with a backtrace but since then has just vanished from sight. If I can get another backtrace, I'll post it. If I leave the tabs settings at their default 8 spaces, this does not happen; all works fine.

I also notice that the editor stubbornly refuses to remember that I set the tabs to four spaces. Whenever I reopen a file or open a new file, the tab setting reverts to 8.

Frequently, the auto-spacing of new lines seems off. If I go into the QtEditor settings and change tabs from 4 to 4 (yes, that is correct, from 4 to 4), the auto-spacing problem goes away for that line.

Finally, I have absurd problems with undoing changes. I'm not sure if this is the same as a similarly reported bug. It almost appears to be related to the tab spacing issue. It appears to sometimes leave what I thought were phantom characters but now appear to really be characters left over from faulty calculation of line length by counting eight spaces (perhaps from an improper reformatting of tabs from eight to four spaces) as four spaces and leaving behind four characters. I've yet to confirm that.

The real critical issue is the crash.

Comment 1 John A. Sullivan III 2004-01-03 00:01:02 UTC

Ooops! I spoke a little too soon.  This did work for me with the default tab settings when I quickly tried it after the first four crashes but I've just tried with tabs set to their default and it crashed on me anyway.  Here is the backtrace:

[New Thread 16384 (LWP 9005)]
[New Thread 32769 (LWP 9033)]
[New Thread 16386 (LWP 9034)]
0x4142976a in waitpid () from /lib/i686/libpthread.so.0
#0  0x4142976a in waitpid () from /lib/i686/libpthread.so.0
#1  0x40a8857d in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#2  0x4142867e in __pthread_sighandler () from /lib/i686/libpthread.so.0
#3  <signal handler called>
#4  0x4230c228 in QEditorView::find_real(QTextParagraph*, int, QTextParagraph*, int) () from /usr/local/kde/lib/kde3/libqeditorpart.so
#5  0x4230bf29 in QEditorView::proceed() ()
   from /usr/local/kde/lib/kde3/libqeditorpart.so
#6  0x4230c708 in QEditorView::doFind() ()
   from /usr/local/kde/lib/kde3/libqeditorpart.so
#7  0x4230e938 in QEditorView::qt_invoke(int, QUObject*) ()
   from /usr/local/kde/lib/kde3/libqeditorpart.so
#8  0x40edb0c9 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#9  0x40edaf6d in QObject::activate_signal(int) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#10 0x40849c7b in KAction::activated() () from /usr/lib/libkdeui.so.4
#11 0x4083b10f in KAction::slotActivated() () from /usr/lib/libkdeui.so.4
#12 0x40849e81 in KAction::qt_invoke(int, QUObject*) ()
   from /usr/lib/libkdeui.so.4
#13 0x40edb0c9 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#14 0x40edaf6d in QObject::activate_signal(int) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#15 0x40a833eb in KAccelPrivate::menuItemActivated() ()
   from /usr/lib/libkdecore.so.4
#16 0x40a81c21 in KAccelPrivate::eventFilter(QObject*, QEvent*) ()
   from /usr/lib/libkdecore.so.4
#17 0x40ed8dee in QObject::activate_filters(QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#18 0x40ed8d11 in QObject::event(QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#19 0x40f0ef8c in QWidget::event(QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#20 0x40fb5ae2 in QMainWindow::event(QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#21 0x403651d6 in KMdiMainFrm::event(QEvent*) ()
   from /usr/local/kde/lib/libkdevelopqextmdi.so.3
#22 0x40e7cf24 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#23 0x40e7cab7 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#24 0x40a1c1e9 in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/libkdecore.so.4
#25 0x40a80c51 in KAccelEventHandler::x11Event(_XEvent*) ()
   from /usr/lib/libkdecore.so.4
#26 0x40a2115f in KApplication::x11EventFilter(_XEvent*) ()
   from /usr/lib/libkdecore.so.4
#27 0x40e17458 in qt_set_x11_event_filter(int (*)(_XEvent*)) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#28 0x40e2076e in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#29 0x40e35bda in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#30 0x40e90cf6 in QEventLoop::enterLoop() ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#31 0x40e90b98 in QEventLoop::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#32 0x40e7d151 in QApplication::exec() ()
   from /usr/lib/qt-3.1/lib/libqt-mt.so.3
#33 0x08062b7a in main ()
#34 0x414bea67 in __libc_start_main () from /lib/i686/libc.so.6

Comment 2 Jens Dagerbo 2004-01-03 00:33:26 UTC

The crash is a dupe. Please open seperate bugs for any remaining issues.

*** This bug has been marked as a duplicate of 60958 ***