Bug 177852 - kate crashes when using code folding and split screen
Summary: kate crashes when using code folding and split screen
Status: RESOLVED FIXED
Alias: None
Product: kate
Classification: Applications
Component: folding (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-15 14:07 UTC by Oliver Putz
Modified: 2008-12-22 11:49 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 Oliver Putz 2008-12-15 14:07:16 UTC
Version:           3.1.82 (using 4.1.82 (KDE 4.1.82 (KDE 4.2 >= 20081204)), Gentoo)
Compiler:          i686-pc-linux-gnu-gcc
OS:                Linux (i686) release 2.6.26-gentoo-r1

Today I tried to reproduce bug #157754 and I seem to be able to still reproduce it -- more or less. However, as the backtrace I get today seems to be completely different from the backtrace I got for bug #157754 months ago, I decided to open a new bugreport.

Steps to reproduce:

1) Open a long document with code folding
2) Split vertically
3) Go to bottom of page in right view
4) Click with left mouse button in right view
5) Fold some stuff on the right side (view on right side gets updated accordingly)
6) Right click in right view


The backtrace for this crash is:

Application: Kate (kate), signal SIGSEGV
[Current thread is 0 (LWP 19645)]

Thread 2 (Thread 0xb3fbdb90 (LWP 19659)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb685e021 in select () from /lib/libc.so.6
#2  0xb6b4a227 in QProcessManager::run (this=0x8055d58) at io/qprocess_unix.cpp:307
#3  0xb6a7aa24 in QThreadPrivate::start (arg=0x8055d58) at thread/qthread_unix.cpp:191
#4  0xb69f8160 in start_thread (arg=0xb3fbdb90) at pthread_create.c:297
#5  0xb6864c0e in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5d46700 (LWP 19645)):
[KCrash Handler]
#6  0xb71bef67 in QTextLine::cursorToX (this=0xbfa09770, cursorPos=0xbfa09744, edge=QTextLine::Leading) at text/qtextlayout.cpp:2063
#7  0xb44d224d in QTextLine::cursorToX (this=0xbfa09770, cursorPos=5, edge=QTextLine::Leading) at /usr/include/qt4/QtGui/qtextlayout.h:216
#8  0xb451ad64 in KateViewInternal::cursorToCoordinate (this=0x82de6c8, cursor=@0xbfa097fc, realCursor=true, includeBorder=false)
    at /var/tmp/portage/kde-base/kdelibs-4.1.82/work/kdelibs-4.1.82/kate/view/kateviewinternal.cpp:733
#9  0xb451aed0 in KateViewInternal::inputMethodQuery (this=0x82de6c8, query=Qt::ImMicroFocus) at /var/tmp/portage/kde-base/kdelibs-4.1.82/work/kdelibs-4.1.82/kate/view/kateviewinternal.cpp:3642
#10 0xb7528c4d in QXIMInputContext::update (this=0x81bb5c0) at inputmethod/qximinputcontext_x11.cpp:747
#11 0xb7529a5b in QXIMInputContext::setFocusWidget (this=0x81bb5c0, w=0x82de6c8) at inputmethod/qximinputcontext_x11.cpp:603
#12 0xb6fb7322 in QApplicationPrivate::setFocusWidget (focus=0x82de6c8, reason=Qt::MouseFocusReason) at kernel/qapplication.cpp:2002
#13 0xb700aa19 in QWidget::setFocus (this=0x832b540, reason=Qt::MouseFocusReason) at kernel/qwidget.cpp:5382
#14 0xb6fb8c62 in QApplication::notify (this=0xbfa0a770, receiver=0x82de6c8, e=0xbfa09ecc) at kernel/qapplication.cpp:3492
#15 0xb7aa3ea7 in KApplication::notify (this=0xbfa0a770, receiver=0x82de6c8, event=0xbfa09ecc) at /var/tmp/portage/kde-base/kdelibs-4.1.82/work/kdelibs-4.1.82/kdeui/kernel/kapplication.cpp:307
#16 0xb6b6bb21 in QCoreApplication::notifyInternal (this=0xbfa0a770, receiver=0x82de6c8, event=0xbfa09ecc) at kernel/qcoreapplication.cpp:593
#17 0xb6fb9879 in QApplicationPrivate::sendMouseEvent (receiver=0x82de6c8, event=0xbfa09ecc, alienWidget=0x82de6c8, nativeWidget=0x82765e8, buttonDown=0xb7776c60, lastMouseReceiver=@0xb7776c64)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#18 0xb70219e7 in QETWidget::translateMouseEvent (this=0x82765e8, event=0xbfa0a3d8) at kernel/qapplication_x11.cpp:4048
#19 0xb702031e in QApplication::x11ProcessEvent (this=0xbfa0a770, event=0xbfa0a3d8) at kernel/qapplication_x11.cpp:3044
#20 0xb704696d in QEventDispatcherX11::processEvents (this=0x80593d8, flags={i = -1079991176}) at kernel/qeventdispatcher_x11.cpp:134
#21 0xb6b6a6b0 in QEventLoop::processEvents (this=0xbfa0a4f0, flags={i = -1079991112}) at kernel/qeventloop.cpp:149
#22 0xb6b6a852 in QEventLoop::exec (this=0xbfa0a4f0, flags={i = -1079991048}) at kernel/qeventloop.cpp:200
#23 0xb6b6cc6f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:851
#24 0xb6fb0d43 in QApplication::exec () at kernel/qapplication.cpp:3337
#25 0xb7eeb0e5 in kdemain (argc=1, argv=0xbfa0acf4) at /var/tmp/portage/kde-base/kate-4.1.82/work/kate-4.1.82/kate/app/katemain.cpp:250
#26 0x08048742 in main (argc=-1216991992, argv=0x830cea8) at /var/tmp/portage/kde-base/kate-4.1.82/work/kate_build/kate/app/kate_dummy.cpp:3
Comment 1 Oliver Putz 2008-12-15 14:11:21 UTC
I also uploaded a video of how to reproduce the crash on http://oliver-putz.de/bugreports/177852.ogv
Comment 2 Dominik Haumann 2008-12-15 17:40:10 UTC
please try again with today's SVN. I committed a patch that might fix this 3 hours ago. Can you retest?
Comment 3 Oliver Putz 2008-12-15 18:09:37 UTC
Ok, I'll try to compile a current svn checkout, retest and report back here :)
Comment 4 Oliver Putz 2008-12-22 11:49:29 UTC
Hi and sorry for the late reply (compiling a current svn checkout gave me some troubles...). Long story short: Seems like this bug indeed has been fixed shortly before I reported it. At least I cannot reproduce it any longer with a current svn checkout. Thanks