Bug 239002 - Random crash of kile
Summary: Random crash of kile
Status: RESOLVED DUPLICATE of bug 239970
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: 2.0.85
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-27 13:11 UTC by Mark van Rossum
Modified: 2010-05-30 23:07 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark van Rossum 2010-05-27 13:11:47 UTC
Application: kile (2.0.85)
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.33.4-95.fc13.i686.PAE i686
Distribution (Platform): Fedora RPMs

-- Information about the crash:
I was just editing, moved the mouse and CRASH.
Nothing special going on otherwise.

The crash can be reproduced some of the time.

 -- Backtrace:
Application: Kile (kile), signal: Segmentation fault
[KCrash Handler]
#6  KateSmartCursor::KateSmartCursor (this=0x99e75b8, position=..., doc=0x8fbd698, insertBehavior=KTextEditor::SmartCursor::MoveOnInsert)
    at /usr/src/debug/kdelibs-4.4.3/kate/smart/katesmartcursor.cpp:50
#7  0x00f3d4ed in KateSmartRange::KateSmartRange (this=0x963b5e8, range=..., doc=0x8fbd698, parent=0x0, insertBehavior=...) at /usr/src/debug/kdelibs-4.4.3/kate/smart/katesmartrange.cpp:36
#8  0x00f42979 in KateSmartManager::newSmartRange (this=0x8fa6d98, range=..., parent=0x0, insertBehavior=..., internal=false) at /usr/src/debug/kdelibs-4.4.3/kate/smart/katesmartmanager.cpp:211
#9  0x00ecebc9 in KateDocument::newSmartRange (this=0x8fbd698, range=..., parent=0x0, insertBehavior=...) at /usr/src/debug/kdelibs-4.4.3/kate/document/katedocument.cpp:4838
#10 0x00f9dd2e in KateIconBorder::showBlock (this=0x911c1e8) at /usr/src/debug/kdelibs-4.4.3/kate/view/kateviewhelpers.cpp:1346
#11 0x00f9e2e3 in KateIconBorder::qt_metacall (this=0x911c1e8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbfadcbdc)
    at /usr/src/debug/kdelibs-4.4.3/i686-redhat-linux-gnu/kate/kateviewhelpers.moc:160
#12 0x04899f1b in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/libQtCore.so.4
#13 0x048a8d3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#14 0x048f0b48 in QTimer::timeout() () from /usr/lib/libQtCore.so.4
#15 0x048aec0e in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4
#16 0x048a51e4 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#17 0x02a24ddc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#18 0x02a2b836 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x036cad9b in KApplication::notify (this=0xbfadd48c, receiver=0x9112528, event=0xbfadd110) at /usr/src/debug/kdelibs-4.4.3/kdeui/kernel/kapplication.cpp:302
#20 0x04895543 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#21 0x048c046e in ?? () from /usr/lib/libQtCore.so.4
#22 0x048bd9b5 in ?? () from /usr/lib/libQtCore.so.4
#23 0x00769525 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#24 0x0076d268 in ?? () from /lib/libglib-2.0.so.0
#25 0x0076d449 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#26 0x048bd6b6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0x02ad3556 in ?? () from /usr/lib/libQtGui.so.4
#28 0x04893c1a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#29 0x04893f5a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x04896627 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#31 0x02a24e88 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#32 0x081de6e3 in _start ()

Possible duplicates by query: bug 237531.

Reported using DrKonqi
Comment 1 Michel Ludwig 2010-05-30 23:07:15 UTC

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