Bug 208312

Summary: Kate crash doing normal usage [KateCodeFoldingNode::getEnd, KateIconBorder::showBlock, KateIconBorder::qt_metacall]
Product: [Applications] kate Reporter: Dario Massarin <nekkar>
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dario Massarin 2009-09-23 17:50:51 UTC
Application: kate (3.3.68)
KDE Version: 4.3.68 (KDE 4.3.68 (KDE 4.4 >= 20090916)) (Compiled from sources)
Qt Version: 4.5.1
Operating System: Linux 2.6.29-gentoo-r5 i686

What I was doing when the application crashed:
Well, I didn't remember doing anything particular when the crash happened. If I remember correctly I was hovering with the mouse the left areas where you can collapse the code.

 -- Backtrace:
Application: Kate (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#5  0xb1fb0b9c in KateCodeFoldingNode::getEnd (this=0x909c598, tree=0x8ede85c, end=0xbfc70478) at /opt/kde/kdelibs/kate/syntax/katecodefolding.cpp:86
#6  0xb1fe3602 in KateIconBorder::showBlock (this=0x8ecac18) at /opt/kde/kdelibs/kate/view/kateviewhelpers.cpp:1301
#7  0xb1fe3b34 in KateIconBorder::qt_metacall (this=0x8ecac18, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfc70578) at /opt/kde/kdelibs_build/kate/kateviewhelpers.moc:148
#8  0xb7fabb12 in QMetaObject::activate (sender=0x8ecaa58, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3117
#9  0xb7facef1 in QMetaObject::activate (sender=0x8ecaa58, m=0xb8051904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3194
#10 0xb7fe9bb1 in QTimer::timeout (this=0x8ecaa58) at .moc/debug-shared/moc_qtimer.cpp:128
#11 0xb7fb466c in QTimer::timerEvent (this=0x8ecaa58, e=0xbfc70b44) at kernel/qtimer.cpp:261
#12 0xb7fa990a in QObject::event (this=0x8ecaa58, e=0xbfc70b44) at kernel/qobject.cpp:1082
#13 0xb6abb24d in QApplicationPrivate::notify_helper (this=0x8751178, receiver=0x8ecaa58, e=0xbfc70b44) at kernel/qapplication.cpp:4057
#14 0xb6abb601 in QApplication::notify (this=0xbfc70e08, receiver=0x8ecaa58, e=0xbfc70b44) at kernel/qapplication.cpp:3604
#15 0xb753169d in KApplication::notify (this=0xbfc70e08, receiver=0x8ecaa58, event=0xbfc70b44) at /opt/kde/kdelibs/kdeui/kernel/kapplication.cpp:302
#16 0xb7f95683 in QCoreApplication::notifyInternal (this=0xbfc70e08, receiver=0x8ecaa58, event=0xbfc70b44) at kernel/qcoreapplication.cpp:606
#17 0xb7f99211 in QCoreApplication::sendEvent (receiver=0x8ecaa58, event=0xbfc70b44) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 0xb7fc77d5 in QTimerInfoList::activateTimers (this=0x8753834) at kernel/qeventdispatcher_unix.cpp:572
#19 0xb7fc5121 in timerSourceDispatch (source=0x8753800) at kernel/qeventdispatcher_glib.cpp:164
#20 0xb662f5a1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb6632aeb in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x08752c38 in ?? ()
#23 0x00000000 in ?? ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-09-25 02:32:23 UTC
Merging with bug 180082. Thanks

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