Bug 264654 - Segmentation fault, no apperant reason for crash
Summary: Segmentation fault, no apperant reason for crash
Status: RESOLVED DUPLICATE of bug 180082
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-28 16:56 UTC by madman
Modified: 2011-01-29 13:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description madman 2011-01-28 16:56:16 UTC
Application: kate (3.4.5)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-27-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
I had a some .phtml files open (Magentos html/php files)
Then I surfed some in Opera and then KATE crashed.
I wasn't currently editing any files.
KATE has been up and running all day, and I never noticed any problem.


 -- Backtrace:
Application: Kate (kate), signal: Segmentation fault
[KCrash Handler]
#6  KateCodeFoldingNode::getEnd (this=0xa0a4778, tree=0x88c0ecc, end=0xbfb62490) at ../../kate/syntax/katecodefolding.cpp:86
#7  0x01ae2236 in KateIconBorder::showBlock (this=0x97d0540) at ../../kate/view/kateviewhelpers.cpp:1318
#8  0x01ae2a13 in KateIconBorder::qt_metacall (this=0x97d0540, _c=QMetaObject::InvokeMetaMethod, _id=31, _a=0xbfb6261c) at ./kateviewhelpers.moc:160
#9  0x0084bc9a in QMetaObject::metacall (object=0x97d0540, cl=143396556, idx=31, argv=0xbfb6261c) at kernel/qmetaobject.cpp:237
#10 0x0085a3d5 in QMetaObject::activate (sender=0x945c128, m=0x95a5a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#11 0x008abaa7 in QTimer::timeout (this=0x945c128) at .moc/release-shared/moc_qtimer.cpp:134
#12 0x0086260e in QTimer::timerEvent (this=0x945c128, e=0xbfb62b50) at kernel/qtimer.cpp:271
#13 0x00857254 in QObject::event (this=0x945c128, e=0xbfb62490) at kernel/qobject.cpp:1212
#14 0x00c6b4dc in QApplicationPrivate::notify_helper (this=0x85b1aa8, receiver=0x945c128, e=0xbfb62b50) at kernel/qapplication.cpp:4300
#15 0x00c7205e in QApplication::notify (this=0xbfb62f04, receiver=0x945c128, e=0xbfb62b50) at kernel/qapplication.cpp:3704
#16 0x0577440a in KApplication::notify (this=0xbfb62f04, receiver=0x945c128, event=0xbfb62b50) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x00846a3b in QCoreApplication::notifyInternal (this=0xbfb62f04, receiver=0x945c128, event=0xbfb62b50) at kernel/qcoreapplication.cpp:704
#18 0x00875d66 in QCoreApplication::sendEvent (this=0x85b3ec4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 QTimerInfoList::activateTimers (this=0x85b3ec4) at kernel/qeventdispatcher_unix.cpp:603
#20 0x008728e4 in timerSourceDispatch (source=0x85b3e90) at kernel/qeventdispatcher_glib.cpp:184
#21 0x01ef75e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0x01efb2d8 in ?? () from /lib/libglib-2.0.so.0
#23 0x01efb4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0x008725d5 in QEventDispatcherGlib::processEvents (this=0x85934a0, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#25 0x00d2b135 in QGuiEventDispatcherGlib::processEvents (this=0x85934a0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#26 0x00845059 in QEventLoop::processEvents (this=0xbfb62e14, flags=) at kernel/qeventloop.cpp:149
#27 0x008454aa in QEventLoop::exec (this=0xbfb62e14, flags=...) at kernel/qeventloop.cpp:201
#28 0x0084969f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#29 0x00c6b577 in QApplication::exec () at kernel/qapplication.cpp:3579
#30 0x006d8a65 in kdemain (argc=2, argv=0xbfb635a4) at ../../../kate/app/katemain.cpp:377
#31 0x080485fb in main (argc=2, argv=0xbfb635a4) at kate_dummy.cpp:3

Possible duplicates by query: bug 257929, bug 256915, bug 245443.

Reported using DrKonqi
Comment 1 Dario Andres 2011-01-29 13:50:32 UTC
[Comment from a bug triager]
This issue is being tracked at bug 180082. Merging. Thanks

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