Bug#701463: kate: Kate crashes when selected text is deleted
Bug unfortunately still present in debian jessie 8.0 $ kate --version Qt: 4.8.6 KDE: 4.14.2 Kate: 3.14.2 best regards, Markus Raab -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701463: kate: Kate crashes when selected text is deleted
On Sat 30 Mar 2013 17:48:16 Markus Raab escribió: [snip] > Hopefully we are still on time, here is the patch (see also in attachment): Saddly we are not, the RT is only accepting bugs of RC severity, which this bug is not :-( It will be fixed in Jessie, that's for sure :-) Kinds regards, Lisandro. -- I still maintain the point that designing a monolithic kernel in 1991 is a fundamental error. Be thankful you are not my student. You would not get a high grade for such a design :-) (Andrew Tanenbaum to Linus Torvalds) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#701463: kate: Kate crashes when selected text is deleted
Tags: patch
Hello!
Am Sonntag, 24. Februar 2013 schrieben Sie:
> On Sun 24 Feb 2013 08:43:19 Markus Raab escribió:
> > Hello!
> >
> >
> >
> > Am Sonntag, 24. Februar 2013 schrieben Sie:
> > > maybe you forgot a press of Escape here? Else you will continue to
> > > write letters.
> >
> >
> >
> > Ok, now the complete sequence to type in to get it crashed (on a new
> > document or the end of an existing document):
> > iabcv+d
>
> Now I could reproduce it!
>
> [snip]
Perfectly!
> > > Anyway, this is an upstream bug, and the only way to get it fixed is to
> > > file a bug upstream.
> >
> >
> >
> > It is already filed upstream: https://bugs.kde.org/show_bug.cgi?id=315683
>
> Indeed, I even marked it as such. My bad :-/ Sorry for the noise :-)
No problem.
> > But maybe it is already fixed in a later kde version and the problem only
> > exists in wheezy.
>
> [snip]
>
> > Can you fix it for wheezy if an patch is available?
>
> I think we are still on time, but we need a patch for that.
Hopefully we are still on time, here is the patch (see also in attachment):
diff --git a/part/vimode/katevinormalmode.cpp
b/part/vimode/katevinormalmode.cpp
index fb6b899..4893736 100644
--- a/part/vimode/katevinormalmode.cpp
+++ b/part/vimode/katevinormalmode.cpp
@@ -698,6 +698,9 @@ bool KateViNormalMode::commandDeleteToEOL()
if ( c.line() < 0 ) {
c.setLine( 0 );
}
+ if ( c.line() > doc()->lastLine() ) {
+c.setLine( doc()->lastLine() );
+ }
if ( c.column() > doc()->lineLength( c.line() )-1 ) {
c.setColumn( doc()->lineLength( c.line() )-1 );
}
And see also:
https://projects.kde.org/projects/kde/applications/kate/repository/revisions/e88d0d35c6e3cb40692a811f335a99cd79f0beaa/diff/part/vimode/katevinormalmode.cpp
https://bugs.kde.org/show_bug.cgi?id=300296
Would be great to see that fix in wheezy!
I tested it already and got no more crashes in kate or kdevelop when this
patch is applied!
best regards
Markus
Description: Fix crash when text is deleted to EOF
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: upstream,
https://projects.kde.org/projects/kde/applications/kate/repository/revisions/e88d0d35c6e3cb40692a811f335a99cd79f0beaa/diff/part/vimode/katevinormalmode.cpp
Bug: https://bugs.kde.org/show_bug.cgi?id=300296
Bug-Debian: http://bugs.debian.org/701463
--- kate-4.8.4.orig/part/vimode/katevinormalmode.cpp
+++ kate-4.8.4/part/vimode/katevinormalmode.cpp
@@ -698,6 +698,9 @@ bool KateViNormalMode::commandDeleteToEO
if ( c.line() < 0 ) {
c.setLine( 0 );
}
+ if ( c.line() > doc()->lastLine() ) {
+c.setLine( doc()->lastLine() );
+ }
if ( c.column() > doc()->lineLength( c.line() )-1 ) {
c.setColumn( doc()->lineLength( c.line() )-1 );
}
Bug#701463: kate: Kate crashes when selected text is deleted
I too got the crash on a 32-bit system, but after upgrading to kde 4.9.5 from qt-kde2.debian.net, the crash did'nt occur any more. Reinhard -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#701463: kate: Kate crashes when selected text is deleted
Control: tag -1 - moreinfo Control: tag -1 confirmed On Sun 24 Feb 2013 08:43:19 Markus Raab escribió: > Hello! > > Am Sonntag, 24. Februar 2013 schrieben Sie: > > maybe you forgot a press of Escape here? Else you will continue to write > > letters. > > Ok, now the complete sequence to type in to get it crashed (on a new > document or the end of an existing document): > iabcv+d Now I could reproduce it! [snip] > > Anyway, this is an upstream bug, and the only way to get it fixed is to > > file a bug upstream. > > It is already filed upstream: https://bugs.kde.org/show_bug.cgi?id=315683 Indeed, I even marked it as such. My bad :-/ Sorry for the noise :-) > But maybe it is already fixed in a later kde version and the problem only > exists in wheezy. [snip] > Can you fix it for wheezy if an patch is available? I think we are still on time, but we need a patch for that. Kinds regards, Lisandro. -- 3: Que ocurre en el escritorio de Windows cuando se abre una ventana * Se cierra una puerta Damian Nadales http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#701463: kate: Kate crashes when selected text is deleted
Hello! Am Sonntag, 24. Februar 2013 schrieben Sie: > maybe you forgot a press of Escape here? Else you will continue to write > letters. Ok, now the complete sequence to type in to get it crashed (on a new document or the end of an existing document): iabcv+d > > leave the cursor at the very last position and press "v", then the up > > cursor and then "D". > > -> crash, new report attached (seems different then the last one). On > > another i386 laptop I got the same crash report. > > > > > > > > Expected behaviour: last two lines should be deleted. > > Ah, you are seing this only on i386 :-/ > > So far I couldn't reproduce it on amd64. No, the initial bug report was from amd64. Obove sequence was tried on amd64, see crash report attached. So I could reproduce it on i386 and amd64. (the backtrace seems to differ quite a lot, but that might be unrelated to the architecture) > Anyway, this is an upstream bug, and the only way to get it fixed is to > file a bug upstream. It is already filed upstream: https://bugs.kde.org/show_bug.cgi?id=315683 But maybe it is already fixed in a later kde version and the problem only exists in wheezy. > Please report it via kate's Help -> Report bug... menu item or by visiting > https://bugs.kde.org/ and following instructions to report a new bug. Can you fix it for wheezy if an patch is available? I reported it on the debian bug reporter in the hope it might be fixed in wheezy because it is a very annoying bug for usability. > Whenever you open a bug report on the KDE bug tracking system, or > you find that the bug has been already reported on it, you can couple > both this Debian bug and the KDE bug together by sending a mail with > the text below to cont...@bugs.debian.org (replace KDE-BUG-URL with > the address of the bug report on https://bugs.kde.org/) Thanks for the information! Wasn't this already done by you in the last mail: "forwarded -1 https://bugs.kde.org/show_bug.cgi?id=315683"; best regards Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f8bbceb7760 (LWP 6118))] Thread 2 (Thread 0x7f8ba91ec700 (LWP 6119)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f8baa322e77 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f8baa630640) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7f8baa322ea9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7f8bb9e16b50 in start_thread (arg=) at pthread_create.c:304 #4 0x7f8bbc822a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7f8bbceb7760 (LWP 6118)): [KCrash Handler] #6 KateLineLayout::viewLineCount (this=0x0) at ../../part/render/katelinelayout.cpp:173 #7 0x7f8baa9b103b in KateLayoutCache::lastViewLine (this=0x0, this@entry=0x14ea9c0, realLine=21932480) at ../../part/render/katelayoutcache.cpp:461 #8 0x7f8baa9b1089 in KateLayoutCache::viewLineCount (this=this@entry=0x14ea9c0, realLine=) at ../../part/render/katelayoutcache.cpp:466 #9 0x7f8baa9b1661 in KateLayoutCache::displayViewLine (this=0x14ea9c0, virtualCursor=..., limitToVisible=true) at ../../part/render/katelayoutcache.cpp:437 #10 0x7f8baa9fc058 in KateViewInternal::cursorToCoordinate (this=this@entry=0x1725710, cursor=..., realCursor=realCursor@entry=true, includeBorder=includeBorder@entry=false) at ../../part/view/kateviewinternal.cpp:715 #11 0x7f8baaa00376 in KateViewInternal::inputMethodQuery (this=0x1725710, query=) at ../../part/view/kateviewinternal.cpp:3415 #12 0x7f8bbc218bb4 in QXIMInputContext::update (this=) at inputmethod/qximinputcontext_x11.cpp:819 #13 0x7f8bbbcb0218 in QWidget::updateMicroFocus (this=0x1725710) at kernel/qwidget.cpp:11389 #14 0x7f8baaa009c1 in KateViewInternal::updateCursor (this=0x1725710, newCursor=..., force=, center=false, calledExternally=false) at ../../part/view/kateviewinternal.cpp:1857 #15 0x7f8baaa1f20d in KateViNormalMode::commandDeleteToEOL (this=0x1834eb0) at ../../part/vimode/katevinormalmode.cpp:708 #16 0x7f8baaa2b5b6 in KateViNormalMode::executeCommand (this=this@entry=0x1834eb0, cmd=cmd@entry=0x183ad80) at ../../part/vimode/katevinormalmode.cpp:433 #17 0x7f8baaa2c6c0 in KateViNormalMode::handleKeypress (this=0x1834eb0, e=) at ../../part/vimode/katevinormalmode.cpp:362 #18 0x7f8baaa14404 in KateViInputModeManager::handleKeypress (this=0x182e4d0, e=0x7fffa958f410) at ../../part/vimode/kateviinputmodemanager.cpp:102 #19 0x7f8baaa05efe in keyPressEvent (e=0x7fffa958f410, this=0x1725710) at ../../part/view/kateviewinternal.cpp:2282 #20 KateViewInternal::keyPressEvent (this=0x1725710, e=0x7fffa958f410) at ../../part/view/kateviewinternal.cpp:2215 #21
Bug#701463: kate: Kate crashes when selected text is deleted
Control: tag -1 upstream On Sat 23 Feb 2013 14:31:46 Markus Raab escribió: > Hello! > > Lisandro Damián Nicanor Pérez Meyer wrote: > > Hi! I'm unable to reproduce this bug in any of my machines. We also have > > not received any complaints of this kind of behaviour from kate from > > other users, and I really think kate is used a lot, so I'm suspecting a > > problem in your side. > > First thank you for your effort! > > I cant really guarantee that there are problems in my configuration (even > though I tried it with complete new users and on three indepently installed > machines), but I am afraid there are some (very annoying!) bugs left in > kate, at least in VI mode. I hope it can be fixed for wheezy. > > This is the most important bug and the easiest one to reproduce. I hope the > instructions below are more clear. > > > Please create a new user account and try again. If you can't reproduce it > > there, then the problem may be in a personal config file. Else, maybe you > > have some corrupted package. > > I installed the debian package and debtags tells me all md5 sums are ok. > > > Of course, if you can reproduce this in another system, please try being > > more explicit on how to reproduce it, maybe there is something I'm > > missing when I'm trying it (I've followed all your steps). > > Open kate (even on a complete new kde user), alt+f2, type "kate" > klick close for the tipps > go into the menu and change the mode to VI: > settings -> configure kate -> editing -> vi input mode -> Use Vi input mode > press ok > insert following text (between ---) by pressing "i" and then typing the > text: --- > a > b > c > --- maybe you forgot a press of Escape here? Else you will continue to write letters. > leave the cursor at the very last position and press "v", then the up > cursor and then "D". > -> crash, new report attached (seems different then the last one). On > another i386 laptop I got the same crash report. > > Expected behaviour: last two lines should be deleted. Ah, you are seing this *only* on i386 :-/ So far I couldn't reproduce it on amd64. Anyway, this is an upstream bug, and the only way to get it fixed is to file a bug upstream. Please report it via kate's Help -> Report bug... menu item or by visiting https://bugs.kde.org/ and following instructions to report a new bug. Whenever you open a bug report on the KDE bug tracking system, or you find that the bug has been already reported on it, you can couple both this Debian bug and the KDE bug together by sending a mail with the text below to cont...@bugs.debian.org (replace KDE-BUG-URL with the address of the bug report on https://bugs.kde.org/) [ copy this ] forwarded KDE-BUG-URL thanks [ copy this ] Kinds regards, Lisandro. -- Un viejo proverbio de El.Machi dice que la memoria es como las papas fritas... ¡nunca sobran! Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#701463: kate: Kate crashes when selected text is deleted
Hello! Lisandro Damián Nicanor Pérez Meyer wrote: > Hi! I'm unable to reproduce this bug in any of my machines. We also have > not received any complaints of this kind of behaviour from kate from other > users, and I really think kate is used a lot, so I'm suspecting a problem > in your side. First thank you for your effort! I cant really guarantee that there are problems in my configuration (even though I tried it with complete new users and on three indepently installed machines), but I am afraid there are some (very annoying!) bugs left in kate, at least in VI mode. I hope it can be fixed for wheezy. This is the most important bug and the easiest one to reproduce. I hope the instructions below are more clear. > Please create a new user account and try again. If you can't reproduce it > there, then the problem may be in a personal config file. Else, maybe you > have some corrupted package. I installed the debian package and debtags tells me all md5 sums are ok. > Of course, if you can reproduce this in another system, please try being > more explicit on how to reproduce it, maybe there is something I'm missing > when I'm trying it (I've followed all your steps). Open kate (even on a complete new kde user), alt+f2, type "kate" klick close for the tipps go into the menu and change the mode to VI: settings -> configure kate -> editing -> vi input mode -> Use Vi input mode press ok insert following text (between ---) by pressing "i" and then typing the text: --- a b c --- leave the cursor at the very last position and press "v", then the up cursor and then "D". -> crash, new report attached (seems different then the last one). On another i386 laptop I got the same crash report. Expected behaviour: last two lines should be deleted. best regards Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fbe8b84a760 (LWP 821))] Thread 2 (Thread 0x7fbe77a00700 (LWP 822)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fbe78d1ce77 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fbe7902a640) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7fbe78d1cea9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7fbe887a9b50 in start_thread (arg=) at pthread_create.c:304 #4 0x7fbe8b1b5a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7fbe8b84a760 (LWP 821)): [KCrash Handler] #6 QTextLine::cursorToX (this=0x7fffa4d9d448, cursorPos=0x7fffa4d9d38c, edge=QTextLine::Leading) at text/qtextlayout.cpp:2494 #7 0x7fbe793a4fb6 in cursorToX (edge=QTextLine::Leading, cursorPos=0, this=) at /usr/include/qt4/QtGui/qtextlayout.h:230 #8 KateRenderer::cursorToX (this=this@entry=0x16edab0, range=..., pos=...) at ../../part/render/katerenderer.cpp:984 #9 0x7fbe793a505e in KateRenderer::cursorToX (this=0x16edab0, range=..., pos=..., returnPastLine=false) at ../../part/render/katerenderer.cpp:989 #10 0x7fbe793f9c3a in KateViewInternal::makeVisible (this=this@entry=0x16f2ce0, c=..., endCol=0, force=force@entry=false, center=center@entry=false, calledExternally=calledExternally@entry=false) at ../../part/view/kateviewinternal.cpp:641 #11 0x7fbe793facdf in KateViewInternal::updateCursor (this=0x16f2ce0, newCursor=..., force=, center=false, calledExternally=false) at ../../part/view/kateviewinternal.cpp:1847 #12 0x7fbe7941920d in KateViNormalMode::commandDeleteToEOL (this=0x2475030) at ../../part/vimode/katevinormalmode.cpp:708 #13 0x7fbe794255b6 in KateViNormalMode::executeCommand (this=this@entry=0x2475030, cmd=cmd@entry=0x1be4ee0) at ../../part/vimode/katevinormalmode.cpp:433 #14 0x7fbe794266c0 in KateViNormalMode::handleKeypress (this=0x2475030, e=) at ../../part/vimode/katevinormalmode.cpp:362 #15 0x7fbe7940e404 in KateViInputModeManager::handleKeypress (this=0x1ce5e00, e=0x7fffa4d9dfd0) at ../../part/vimode/kateviinputmodemanager.cpp:102 #16 0x7fbe793ffefe in keyPressEvent (e=0x7fffa4d9dfd0, this=0x16f2ce0) at ../../part/view/kateviewinternal.cpp:2282 #17 KateViewInternal::keyPressEvent (this=0x16f2ce0, e=0x7fffa4d9dfd0) at ../../part/view/kateviewinternal.cpp:2215 #18 0x7fbe793f822b in KateViewInternal::eventFilter (this=0x16f2ce0, obj=0x16f2ce0, e=0x7fffa4d9dfd0) at ../../part/view/kateviewinternal.cpp:2167 #19 0x7fbe89079cc6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=, receiver=0x16f2ce0, event=0x7fffa4d9dfd0) at kernel/qcoreapplication.cpp:1025 #20 0x7fbe8a6016dc in QApplicationPrivate::notify_helper (this=this@entry=0x125c660, receiver=receiver@entry=0x16f2ce0, e=e@entry=0x7fffa4d9dfd0) at kernel/qapplication.cpp:4552 #21 0x7fbe8a606704 in QApplication::notif
Bug#701463: kate: Kate crashes when selected text is deleted
tag -1 unreproducible moreinfo forwarded -1 https://bugs.kde.org/show_bug.cgi?id=315683 thanks On Sat 23 Feb 2013 09:00:56 Markus Raab escribió: [snip] > See also https://bugs.kde.org/show_bug.cgi?id=315683 > > Application: kate (3.8.4) > KDE Platform Version: 4.8.4 (4.8.4) > Qt Version: 4.8.2 > Operating System: Linux 3.2.0-4-amd64 x86_64 > Distribution: Debian GNU/Linux 7.0 (wheezy) > > -- Information about the crash: > - What I was doing when the application crashed: > > I selected Text (either with V in vim mode or with mouse) at the very > bottom (including the last line!) of a text document. When I press D (for > deleting text) kate crashes. > > - Custom settings of the application: > > The VI-Insert mode is active > (but not the overwrite of kate and without status) > > The crash can be reproduced every time. Hi! I'm unable to reproduce this bug in any of my machines. We also have not received any complaints of this kind of behaviour from kate from other users, and I really think kate is used a lot, so I'm suspecting a problem in your side. Please create a new user account and try again. If you can't reproduce it there, then the problem may be in a personal config file. Else, maybe you have some corrupted package. Of course, if you can reproduce this in another system, please try being more explicit on how to reproduce it, maybe there is something I'm missing when I'm trying it (I've followed all your steps). Kinds regards, Lisandro. -- Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Anonymous Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#701463: kate: Kate crashes when selected text is deleted
Package: kate Version: 4:4.8.4-1 Severity: normal Tags: upstream See also https://bugs.kde.org/show_bug.cgi?id=315683 Application: kate (3.8.4) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.2.0-4-amd64 x86_64 Distribution: Debian GNU/Linux 7.0 (wheezy) -- Information about the crash: - What I was doing when the application crashed: I selected Text (either with V in vim mode or with mouse) at the very bottom (including the last line!) of a text document. When I press D (for deleting text) kate crashes. - Custom settings of the application: The VI-Insert mode is active (but not the overwrite of kate and without status) The crash can be reproduced every time. -- Backtrace: Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe302cc1760 (LWP 6465))] Thread 2 (Thread 0x7fe2eeff6700 (LWP 6520)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fe2f012ce77 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7fe2f043a640) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x7fe2f012cea9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x7fe2ffc20b50 in start_thread (arg=) at pthread_create.c:304 #4 0x7fe30262ca7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 1 (Thread 0x7fe302cc1760 (LWP 6465)): [KCrash Handler] #6 KateLineLayout::viewLineCount (this=0x0) at ../../part/render/katelinelayout.cpp:173 #7 0x7fe2f07bb03b in KateLayoutCache::lastViewLine (this=0x0, this@entry=0x18b81c0, realLine=25919936) at ../../part/render/katelayoutcache.cpp:461 #8 0x7fe2f07bb089 in KateLayoutCache::viewLineCount (this=this@entry=0x18b81c0, realLine=) at ../../part/render/katelayoutcache.cpp:466 #9 0x7fe2f07bb661 in KateLayoutCache::displayViewLine (this=0x18b81c0, virtualCursor=..., limitToVisible=true) at ../../part/render/katelayoutcache.cpp:437 #10 0x7fe2f0806058 in KateViewInternal::cursorToCoordinate (this=this@entry=0x18b8750, cursor=..., realCursor=realCursor@entry=true, includeBorder=includeBorder@entry=false) at ../../part/view/kateviewinternal.cpp:715 #11 0x7fe2f080a376 in KateViewInternal::inputMethodQuery (this=0x18b8750, query=) at ../../part/view/kateviewinternal.cpp:3415 #12 0x7fe302022bb4 in QXIMInputContext::update (this=) at inputmethod/qximinputcontext_x11.cpp:819 #13 0x7fe301aba218 in QWidget::updateMicroFocus (this=0x18b8750) at kernel/qwidget.cpp:11389 #14 0x7fe2f080a9c1 in KateViewInternal::updateCursor (this=0x18b8750, newCursor=..., force=, center=false, calledExternally=false) at ../../part/view/kateviewinternal.cpp:1857 #15 0x7fe2f082920d in KateViNormalMode::commandDeleteToEOL (this=0x1a5c900) at ../../part/vimode/katevinormalmode.cpp:708 #16 0x7fe2f08355b6 in KateViNormalMode::executeCommand (this=this@entry=0x1a5c900, cmd=cmd@entry=0x1a62880) at ../../part/vimode/katevinormalmode.cpp:433 #17 0x7fe2f08366c0 in KateViNormalMode::handleKeypress (this=0x1a5c900, e=) at ../../part/vimode/katevinormalmode.cpp:362 #18 0x7fe2f081e404 in KateViInputModeManager::handleKeypress (this=0x1a42e20, e=0x7fffcdbb5500) at ../../part/vimode/kateviinputmodemanager.cpp:102 #19 0x7fe2f080fefe in keyPressEvent (e=0x7fffcdbb5500, this=0x18b8750) at ../../part/view/kateviewinternal.cpp:2282 #20 KateViewInternal::keyPressEvent (this=0x18b8750, e=0x7fffcdbb5500) at ../../part/view/kateviewinternal.cpp:2215 #21 0x7fe2f080822b in KateViewInternal::eventFilter (this=0x18b8750, obj=0x18b8750, e=0x7fffcdbb5500) at ../../part/view/kateviewinternal.cpp:2167 #22 0x7fe3004f0cc6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=, receiver=0x18b8750, event=0x7fffcdbb5500) at kernel/qcoreapplication.cpp:1025 #23 0x7fe301a786dc in QApplicationPrivate::notify_helper (this=this@entry=0x11fd590, receiver=receiver@entry=0x18b8750, e=e@entry=0x7fffcdbb5500) at kernel/qapplication.cpp:4552 #24 0x7fe301a7d704 in QApplication::notify (this=, receiver=0x18b8750, e=0x7fffcdbb5500) at kernel/qapplication.cpp:3997 #25 0x7fe300d1e886 in KApplication::notify (this=0x7fffcdbb6760, receiver=0x18b8750, event=0x7fffcdbb5500) at ../../kdeui/kernel/kapplication.cpp:311 #26 0x7fe3004f0b5e in QCoreApplication::notifyInternal (this=0x7fffcdbb6760, receiver=0x18b8750, event=0x7fffcdbb5500) at kernel/qcoreapplication.cpp:915 #27 0x7fe301b15a9a in QKeyMapper::sendKeyEvent (keyWidget=keyWidget@entry=0x18b8750, grab=grab@entry=false, type=QEvent::KeyPress, code=68, modifiers=..., text=..., autorepeat=autorepeat@entry=false, count=1, nativeScanCode=40, nativeVirtualKey=68, nativeModifiers=1) at kernel/qkeymapper_x11.cpp:1866 #28 0x7fe301b15e
