Bug 245152

Summary: kile crashes with segmentation fault during editing
Product: [Applications] kile Reporter: afylot
Component: generalAssignee: Michel Ludwig <michel.ludwig>
Status: RESOLVED DUPLICATE    
Severity: crash CC: kde
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description afylot 2010-07-19 18:06:11 UTC
Application that crashed: kile
Version of the application: 2.0.83
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-22-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I was editing a file while kile crashed. I must say I had been using it for a long time ~ 8 hours. I have already sent a report yesterday night, but I forgot to say I am running under gnome, I don't know if running kde apps under gnome is raccomended.

 -- Backtrace:
Application: Kile (kile), signal: Segmentation fault
[KCrash Handler]
#6  0x057f9e6a in KateSmartCursor::setPositionInternal (this=0xa7c099c, pos=..., internal=false) at ../../kate/smart/katesmartcursor.cpp:186
#7  0x057fa595 in KateSmartCursor::setPosition (this=0xa7c099c, pos=...) at ../../kate/smart/katesmartcursor.cpp:415
#8  0x05851f20 in KateSmartCursor::operator= (this=0xa7c0948, newCursor=..., force=false, center=false, calledExternally=false) at ../../kate/smart/katesmartcursor.h:68
#9  KateViewInternal::updateCursor (this=0xa7c0948, newCursor=..., force=false, center=false, calledExternally=false) at ../../kate/view/kateviewinternal.cpp:1901
#10 0x0585403e in KateViewInternal::cursorDown (this=0xa7c0948, sel=<value optimized out>) at ../../kate/view/kateviewinternal.cpp:1516
#11 0x0582f2bb in KateView::down (this=0xa8a6ae8) at ../../kate/view/kateview.cpp:2593
#12 0x0583a238 in KateView::qt_metacall (this=0xa8a6ae8, _c=QMetaObject::InvokeMetaMethod, _id=69, _a=0xbfd98fc8) at ./kateview.moc:373
#13 0x04f01263 in QMetaObject::activate (sender=0xa95cde0, from_signal_index=5, to_signal_index=6, argv=0xbfd98fc8) at kernel/qobject.cpp:3113
#14 0x04f016d8 in QMetaObject::activate (sender=0xa95cde0, m=0x1acae48, from_local_signal_index=1, to_local_signal_index=2, argv=0xbfd98fc8) at kernel/qobject.cpp:3207
#15 0x012629b1 in QAction::triggered (this=0xa95cde0, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#16 0x01263f32 in QAction::activate (this=0xa95cde0, event=QAction::Trigger) at kernel/qaction.cpp:1160
#17 0x01266a18 in QAction::event (this=0x0, e=0xd6) at kernel/qaction.cpp:1079
#18 0x04614eb3 in KAction::event (this=0xa95cde0, event=0xbfd99418) at ../../kdeui/actions/kaction.cpp:88
#19 0x01268f54 in QApplicationPrivate::notify_helper (this=0x9d02be0, receiver=0xa95cde0, e=0xbfd99418) at kernel/qapplication.cpp:4056
#20 0x0127067c in QApplication::notify (this=0xbfd9b350, receiver=0xa95cde0, e=0xbfd99418) at kernel/qapplication.cpp:3603
#21 0x046fbbfa in KApplication::notify (this=0xbfd9b350, receiver=0xa95cde0, event=0xbfd99418) at ../../kdeui/kernel/kapplication.cpp:302
#22 0x04eeb6cb in QCoreApplication::notifyInternal (this=0xbfd9b350, receiver=0xa95cde0, event=0xbfd99418) at kernel/qcoreapplication.cpp:610
#23 0x012a1dfd in QCoreApplication::sendEvent (this=0x9d02c80, e=0xbfd997c4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#24 QShortcutMap::dispatchEvent (this=0x9d02c80, e=0xbfd997c4) at kernel/qshortcutmap.cpp:884
#25 0x012a3c7e in QShortcutMap::tryShortcutEvent (this=0x9d02c80, o=0xa7c0948, e=0xbfd997c4) at kernel/qshortcutmap.cpp:369
#26 0x01271a0d in QApplication::notify (this=0xbfd9b350, receiver=0xa7c0948, e=0xbfd997c4) at kernel/qapplication.cpp:3645
#27 0x046fbbfa in KApplication::notify (this=0xbfd9b350, receiver=0xa7c0948, event=0xbfd997c4) at ../../kdeui/kernel/kapplication.cpp:302
#28 0x04eeb6cb in QCoreApplication::notifyInternal (this=0xbfd9b350, receiver=0xa7c0948, event=0xbfd997c4) at kernel/qcoreapplication.cpp:610
#29 0x01269e2e in QCoreApplication::sendSpontaneousEvent (receiver=0xa7c0948, event=0x0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#30 qt_sendSpontaneousEvent (receiver=0xa7c0948, event=0x0) at kernel/qapplication.cpp:4958
#31 0x01306440 in QKeyMapper::sendKeyEvent (keyWidget=0xa7c0948, grab=false, type=QEvent::KeyPress, code=16777237, modifiers=..., text=..., autorepeat=<value optimized out>, 
    count=<value optimized out>, nativeScanCode=116, nativeVirtualKey=65364, nativeModifiers=0) at kernel/qkeymapper_x11.cpp:1861
#32 0x01308989 in QKeyMapperPrivate::translateKeyEvent (this=0x9d28fc8, keyWidget=0xa7c0948, event=0xbfd9afac, grab=214) at kernel/qkeymapper_x11.cpp:1831
#33 0x012dced7 in QApplication::x11ProcessEvent (this=0xbfd9b350, event=0xbfd9afac) at kernel/qapplication_x11.cpp:3443
#34 0x0130a502 in x11EventSourceDispatch (s=0x9d05968, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#35 0x0211ae88 in g_main_dispatch (context=0x9d04c90) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#36 IA__g_main_context_dispatch (context=0x9d04c90) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#37 0x0211e730 in g_main_context_iterate (context=0x9d04c90, block=<value optimized out>, dispatch=1, self=0x9d02818) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#38 0x0211e863 in IA__g_main_context_iteration (context=0x9d04c90, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#39 0x04f1602c in QEventDispatcherGlib::processEvents (this=0x9ce4cc8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#40 0x01309be5 in QGuiEventDispatcherGlib::processEvents (this=0x9ce4cc8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#41 0x04ee9c79 in QEventLoop::processEvents (this=0xbfd9b2a4, flags=) at kernel/qeventloop.cpp:149
#42 0x04eea0ca in QEventLoop::exec (this=0xbfd9b2a4, flags=...) at kernel/qeventloop.cpp:201
#43 0x04eec53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#44 0x01268dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#45 0x081ee3f3 in _start ()

This bug may be a duplicate of or related to bug 245084

Reported using DrKonqi
Comment 1 Nicolas L. 2010-07-20 12:50:24 UTC

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