Application that crashed: kate Version of the application: 3.3.1 KDE Version: 4.3.1 (KDE 4.3.1) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: I was moving between open tabs in kate when it crashed. It seems to happen when more then 15 minutes have gone by. I'm working with php only files. It doesn't seem to matter if I alt-tab between programs only the tabs in kate will crash it. -- Backtrace: Application: Kate (kdeinit4), signal: Segmentation fault [KCrash Handler] #5 KateCodeFoldingNode::getEnd (this=0x591e710, tree=0x59b0170, end=0x7fff08f5f170) at /build/buildd/kde4libs-4.3.1/kate/syntax/katecodefolding.cpp:86 #6 0x00007f06f1155bee in KateIconBorder::showBlock (this=0x59a4d20, line=3) at /build/buildd/kde4libs-4.3.1/kate/view/kateviewhelpers.cpp:1275 #7 0x00007f06f1156c5a in KateIconBorder::mouseMoveEvent (this=0x59a4d20, e=0x7fff08f5fbe0) at /build/buildd/kde4libs-4.3.1/kate/view/kateviewhelpers.cpp:1328 #8 0x00007f06fe067f58 in QWidget::event (this=0x59a4d20, event=0x7fff08f5fbe0) at kernel/qwidget.cpp:7534 #9 0x00007f06fe016f4d in QApplicationPrivate::notify_helper (this=0x1fb0d50, receiver=0x59a4d20, e=0x7fff08f5fbe0) at kernel/qapplication.cpp:4056 #10 0x00007f06fe01f8ea in QApplication::notify (this=<value optimized out>, receiver=0x59a4d20, e=0x7fff08f5fbe0) at kernel/qapplication.cpp:3758 #11 0x00007f06ff129deb in KApplication::notify (this=0x7fff08f61bb0, receiver=0x59a4d20, event=0x7fff08f5fbe0) at /build/buildd/kde4libs-4.3.1/kdeui/kernel/kapplication.cpp:302 #12 0x00007f0700a506ac in QCoreApplication::notifyInternal (this=0x7fff08f61bb0, receiver=0x59a4d20, event=0x7fff08f5fbe0) at kernel/qcoreapplication.cpp:610 #13 0x00007f06fe01eb38 in QApplicationPrivate::sendMouseEvent (receiver=0x59a4d20, event=0x7fff08f5fbe0, alienWidget=0x59a4d20, nativeWidget=0x256e560, buttonDown=<value optimized out>, lastMouseReceiver=@0x7f06fea4e010) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216 #14 0x00007f06fe088b19 in QETWidget::translateMouseEvent (this=0x256e560, event=<value optimized out>) at kernel/qapplication_x11.cpp:4409 #15 0x00007f06fe087b53 in QApplication::x11ProcessEvent (this=0x7fff08f61bb0, event=0x7fff08f61760) at kernel/qapplication_x11.cpp:3550 #16 0x00007f06fe0b0454 in x11EventSourceDispatch (s=0x1fb49b0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #17 0x00007f06fcaaa20a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #18 0x00007f06fcaad8e0 in ?? () from /usr/lib/libglib-2.0.so.0 #19 0x00007f06fcaada7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #20 0x00007f0700a79a8f in QEventDispatcherGlib::processEvents (this=0x1fb0340, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327 #21 0x00007f06fe0afbdf in QGuiEventDispatcherGlib::processEvents (this=0x591e710, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202 #22 0x00007f0700a4ef42 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 150346320}) at kernel/qeventloop.cpp:149 #23 0x00007f0700a4f314 in QEventLoop::exec (this=0x7fff08f61a90, flags={i = 150346400}) at kernel/qeventloop.cpp:201 #24 0x00007f0700a515e4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #25 0x00007f06f49d5dc5 in kdemain () from /usr/lib/libkdeinit4_kate.so #26 0x0000000000407215 in launch (argc=1, _name=0x1f52b78 "/usr/bin/kate", args=<value optimized out>, cwd=0x0, envc=1, envs=0x1f52b9a "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x1f52ba3 "vagabond;1254500441;502167;3304_TIME252069483") at /build/buildd/kde4libs-4.3.1/kinit/kinit.cpp:677 #27 0x0000000000407a38 in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.3.1/kinit/kinit.cpp:1169 #28 0x0000000000407fe5 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.3.1/kinit/kinit.cpp:1362 #29 0x0000000000408b26 in main (argc=2, argv=0x7fff08f63968, envp=0x7fff08f63980) at /build/buildd/kde4libs-4.3.1/kinit/kinit.cpp:1793 Reported using DrKonqi
I wonder how this could happen. The code is: for (KateCodeFoldingNode *n=parentNode;n;n=n->parentNode) line+=n->startLineRel; so the n-Pointer is always checked before accessed... Is this problem reproducable to you? If so, we might need a valgrind run.
The backtrace is mostly like bug 180082, they could be merged... Thanks
Yes indeed Dario! Thanks. How the hell do you manage to find all these duplicates? :D I always wonder! *** This bug has been marked as a duplicate of bug 180082 ***