Version: SVN revision 746549 (using KDE Devel) Installed from: Compiled sources Compiler: gcc (GCC) 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) OS: Linux KWrite was started from a console within a KDE3 session, but it's running as a user set up for KDE4 (according to the How-to at http://techbase.kde.org/Getting_Started/Build/KDE4 I compiled revision 746549). I didn't change any settings, load additional plugins or remove the ones that are activated per default. When opening a file from the "recent files" list, it crashed with the backtrace below. I couldn't reproduce this at all. Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1239841088 (LWP 8481)] [KCrash handler] #5 0xffffe410 in __kernel_vsyscall () #6 0xb6508875 in raise () from /lib/tls/i686/cmov/libc.so.6 #7 0xb650a201 in abort () from /lib/tls/i686/cmov/libc.so.6 #8 0xb6ff9f8d in qt_message_output (msgType=QtFatalMsg, buf=0xbf994540 "ASSERT: \"valid()\" in file /home/kde4/kde/src/KDE/kdelibs/kate/view/kateviewinternal.cpp, line 774") at global/qglobal.cpp:2160 #9 0xb6ffa011 in qFatal (msg=0xb70f0ff0 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2392 #10 0xb6ffa17d in qt_assert (assertion=0xb4900400 "valid()", file=0xb4900264 "/home/kde4/kde/src/KDE/kdelibs/kate/view/kateviewinternal.cpp", line=774) at global/qglobal.cpp:1917 #11 0xb4898e5d in CalculatingCursor (this=0xbf9965dc, vi=0x81dc3f0, c=@0x81dc444) at /home/kde4/kde/src/KDE/kdelibs/kate/view/kateviewinternal.cpp:774 #12 0xb4898ecf in WrappingCursor (this=0xbf9965dc, vi=0x81dc3f0, c=@0x81dc444) at /home/kde4/kde/src/KDE/kdelibs/kate/view/kateviewinternal.cpp:896 #13 0xb48907c3 in KateViewInternal::moveChar (this=0x81dc3f0, bias=KateViewInternal::left, sel=false) at /home/kde4/kde/src/KDE/kdelibs/kate/view/kateviewinternal.cpp:971 #14 0xb4890a03 in KateViewInternal::cursorLeft (this=0x81dc3f0, sel=false) at /home/kde4/kde/src/KDE/kdelibs/kate/view/kateviewinternal.cpp:988 #15 0xb4874959 in KateView::cursorLeft (this=0x81da238) at /home/kde4/kde/src/KDE/kdelibs/kate/view/kateview.cpp:2206 #16 0xb4884557 in KateView::qt_metacall (this=0x81da238, _c=QMetaObject::InvokeMetaMethod, _id=44, _a=0xbf996bbc) at /home/kde4/kde/build/KDE/kdelibs/kate/kateview.moc:315 #17 0xb70c9c3c in QMetaObject::activate (sender=0x82607e8, from_signal_index=5, to_signal_index=6, argv=0xbf996bbc) at kernel/qobject.cpp:3087 #18 0xb70c9e38 in QMetaObject::activate (sender=0x82607e8, m=0xb6edec20, from_local_signal_index=1, to_local_signal_index=2, argv=0xbf996bbc) at kernel/qobject.cpp:3169 #19 0xb68880b8 in QAction::triggered (this=0x82607e8, _t1=false) at .moc/debug-shared/moc_qaction.cpp:208 #20 0xb6889e26 in QAction::activate (this=0x82607e8, event=QAction::Trigger) at kernel/qaction.cpp:1114 #21 0xb6889fd7 in QAction::event (this=0x82607e8, e=0xbf997074) at kernel/qaction.cpp:1033 #22 0xb68eb2cc in QWidgetAction::event (this=0x82607e8, event=0xbf997074) at kernel/qwidgetaction.cpp:216 #23 0xb688fc8d in QApplicationPrivate::notify_helper (this=0x805c3f8, receiver=0x82607e8, e=0xbf997074) at kernel/qapplication.cpp:3556 #24 0xb688ff8e in QApplication::notify (this=0xbf997e8c, receiver=0x82607e8, e=0xbf997074) at kernel/qapplication.cpp:3115 #25 0xb76668db in KApplication::notify (this=0xbf997e8c, receiver=0x82607e8, event=0xbf997074) at /home/kde4/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:319 #26 0xb70b848e in QCoreApplication::notifyInternal (this=0xbf997e8c, receiver=0x82607e8, event=0xbf997074) at kernel/qcoreapplication.cpp:530 #27 0xb688c9bf in QCoreApplication::sendEvent (receiver=0x82607e8, event=0xbf997074) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:200 #28 0xb68c63bd in QShortcutMap::dispatchEvent (this=0x805c484, e=0xbf9974e4) at kernel/qshortcutmap.cpp:751 #29 0xb68c7353 in QShortcutMap::tryShortcutEvent (this=0x805c484, w=0x81dc3f0, e=0xbf9974e4) at kernel/qshortcutmap.cpp:354 #30 0xb68901be in QApplication::notify (this=0xbf997e8c, receiver=0x81dc3f0, e=0xbf9974e4) at kernel/qapplication.cpp:3152 #31 0xb76668db in KApplication::notify (this=0xbf997e8c, receiver=0x81dc3f0, event=0xbf9974e4) at /home/kde4/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:319 #32 0xb70b848e in QCoreApplication::notifyInternal (this=0xbf997e8c, receiver=0x81dc3f0, event=0xbf9974e4) at kernel/qcoreapplication.cpp:530 #33 0xb689b05d in QCoreApplication::sendSpontaneousEvent (receiver=0x81dc3f0, event=0xbf9974e4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:203 #34 0xb68edac0 in qt_sendSpontaneousEvent (receiver=0x81dc3f0, event=0xbf9974e4) at kernel/qapplication_x11.cpp:4395 #35 0xb69245c4 in QKeyMapper::sendKeyEvent (keyWidget=0x81dc3f0, grab=false, type=QEvent::KeyPress, code=16777234, modifiers=@0xbf997694, text=@0xbf99766c, autorepeat=false, count=1, nativeScanCode=100, nativeVirtualKey=65361, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1599 #36 0xb6925950 in QKeyMapperPrivate::translateKeyEvent (this=0x807a4a8, keyWidget=0x81dc3f0, event=0xbf997bac, grab=false) at kernel/qkeymapper_x11.cpp:1579 #37 0xb68fa203 in QApplication::x11ProcessEvent (this=0xbf997e8c, event=0xbf997bac) at kernel/qapplication_x11.cpp:2933 #38 0xb6927d9b in x11EventSourceDispatch (s=0x805f318, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:135 #39 0xb634211c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0xb634555f in ?? () from /usr/lib/libglib-2.0.so.0 #41 0x0805e690 in ?? () #42 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall ()
Hm, a way to reproduce this would be nice. It seems to be another cursor-misplacement bug, but from the backtrace it's not visible, when exactly the cursor became invalid. What the backtrace does show, is that immediately prior to the crash you move the cursor to the left. Perhaps with this info you can find a way to reproduce the crash? That would be very helpful.
I just tried hard and opened about 10 files while moving the mouse as much as I could, but I didn't get any crash. I'm really sorry. If I ever get another KWrite crash, I'll submit the backtrace here.
Ok, please reopen if way to reproduce is there.
Bug 181894 may be related to this (with testcase)