Application: kate (3.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-21-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: I marked a bookmark, then scrolled all the way to the beginning of the document and then went to the bookmark I previously marked with the Bookmarks menu. Kate crashed right after that. I don't know what could have caused this. I had firefox opened, two nautilus windows, and a terminal window. The document was a java source file with more than 1000 lines of code. There were few bookmarks (no more than 8). I don't know if my system information is caugth automatically by this bug report system in kate, but I'll post my system configuration just in case: Software: - Ubuntu Lucid Lynx 10.04 - Kate 3.4.2 Hardware: - Pentium 4 socket 775 3.0 Ghz - 1GB RAM DDR2 533Mhz - 160GB hard disk (8.6 GB partition for Ubuntu with 86% of space used) - ECS GF7050-VT-M Mobo Best regards. The crash does not seem to be reproducible. -- Backtrace: Application: Kate (kate), signal: Segmentation fault [KCrash Handler] #6 KateCodeFoldingNode::getEnd (this=0x9c17930, tree=0x985f4ac, end=0xbf9a9260) at ../../kate/syntax/katecodefolding.cpp:86 #7 0x0277f0f6 in KateIconBorder::showBlock (this=0x98efdb0) at ../../kate/view/kateviewhelpers.cpp:1315 #8 0x0277f8d3 in KateIconBorder::qt_metacall (this=0x98efdb0, _c=QMetaObject::InvokeMetaMethod, _id=31, _a=0xbf9a93ec) at ./kateviewhelpers.moc:160 #9 0x068c5c9a in QMetaObject::metacall (object=0x98efdb0, cl=159773868, idx=31, argv=0xbf9a93ec) at kernel/qmetaobject.cpp:237 #10 0x068d43d5 in QMetaObject::activate (sender=0x98ef418, m=0x69d45a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #11 0x06925aa7 in QTimer::timeout (this=0x98ef418) at .moc/release-shared/moc_qtimer.cpp:134 #12 0x068dc60e in QTimer::timerEvent (this=0x98ef418, e=0xbf9a9920) at kernel/qtimer.cpp:271 #13 0x068d1254 in QObject::event (this=0x98ef418, e=0xbf9a9260) at kernel/qobject.cpp:1212 #14 0x00e974dc in QApplicationPrivate::notify_helper (this=0x929a2d0, receiver=0x98ef418, e=0xbf9a9920) at kernel/qapplication.cpp:4300 #15 0x00e9e05e in QApplication::notify (this=0xbf9a9cd4, receiver=0x98ef418, e=0xbf9a9920) at kernel/qapplication.cpp:3704 #16 0x007caf2a in KApplication::notify (this=0xbf9a9cd4, receiver=0x98ef418, event=0xbf9a9920) at ../../kdeui/kernel/kapplication.cpp:302 #17 0x068c0a3b in QCoreApplication::notifyInternal (this=0xbf9a9cd4, receiver=0x98ef418, event=0xbf9a9920) at kernel/qcoreapplication.cpp:704 #18 0x068efd66 in QCoreApplication::sendEvent (this=0x929c444) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #19 QTimerInfoList::activateTimers (this=0x929c444) at kernel/qeventdispatcher_unix.cpp:603 #20 0x068ec917 in timerSourceDispatch (source=0x929c478) at kernel/qeventdispatcher_glib.cpp:184 #21 idleTimerSourceDispatch (source=0x929c478) at kernel/qeventdispatcher_glib.cpp:231 #22 0x08b785e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #23 0x08b7c2d8 in ?? () from /lib/libglib-2.0.so.0 #24 0x08b7c4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #25 0x068ec5d5 in QEventDispatcherGlib::processEvents (this=0x927b9c0, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #26 0x00f57135 in QGuiEventDispatcherGlib::processEvents (this=0x927b9c0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #27 0x068bf059 in QEventLoop::processEvents (this=0xbf9a9be4, flags=) at kernel/qeventloop.cpp:149 #28 0x068bf4aa in QEventLoop::exec (this=0xbf9a9be4, flags=...) at kernel/qeventloop.cpp:201 #29 0x068c369f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #30 0x00e97577 in QApplication::exec () at kernel/qapplication.cpp:3579 #31 0x00a31a65 in kdemain (argc=2, argv=0xbf9aa374) at ../../../kate/app/katemain.cpp:377 #32 0x080485fb in main (argc=2, argv=0xbf9aa374) at kate_dummy.cpp:3 Possible duplicates by query: bug 245443. Reported using DrKonqi
[Comment from a bug triager] Related crashes are being tracked at bug 180082. Merging. Thanks for the information *** This bug has been marked as a duplicate of bug 180082 ***