Bug 226277 - Kile crashed after source file was externally updated
Summary: Kile crashed after source file was externally updated
Status: RESOLVED DUPLICATE of bug 224229
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-11 11:24 UTC by 81joe81
Modified: 2010-02-15 23:37 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 81joe81 2010-02-11 11:24:20 UTC
Application that crashed: kile
Version of the application: 2.0.83
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-19-generic-pae i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
The tex source file I was working on had been updated externally (by performing a svn update on the console).
Kile crashed immediately after the update completed.

 -- Backtrace:
Application: Kile (kile), signal: Segmentation fault
[KCrash Handler]
#6  0xb57f08e5 in QString::size (this=0x9bb7a98, other=...) at ../../include/QtCore/../../src/corelib/tools/qstring.h:104
#7  QString::operator== (this=0x9bb7a98, other=...) at tools/qstring.cpp:1912
#8  0xb6c3fdaf in KDirWatchPrivate::Entry::findSubEntry (this=0x95bfc38) at ../../kio/kio/kdirwatch_p.h:157
#9  KDirWatchPrivate::inotifyEventReceived (this=0x95bfc38) at ../../kio/kio/kdirwatch.cpp:297
#10 0xb6c414cb in KDirWatchPrivate::qt_metacall (this=0x95bfc38, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfbab1d8) at ./kdirwatch_p.moc:75
#11 0xb58b3263 in QMetaObject::activate (sender=0x95a9458, from_signal_index=4, to_signal_index=4, argv=0xbfbab1d8) at kernel/qobject.cpp:3113
#12 0xb58b3ec2 in QMetaObject::activate (sender=0x95a9458, m=0xb598e8b0, local_signal_index=0, argv=0xbfbab1d8) at kernel/qobject.cpp:3187
#13 0xb58ed503 in QSocketNotifier::activated (this=0x95a9458, _t1=24) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#14 0xb58b7c87 in QSocketNotifier::event (this=0x95a9458, e=0xbfbab594) at kernel/qsocketnotifier.cpp:316
#15 0xb5d71f54 in QApplicationPrivate::notify_helper (this=0x9415a30, receiver=0x95a9458, e=0xbfbab594) at kernel/qapplication.cpp:4056
#16 0xb5d7967c in QApplication::notify (this=0xbfbab8e0, receiver=0x95a9458, e=0xbfbab594) at kernel/qapplication.cpp:3603
#17 0xb681525a in KApplication::notify (this=0xbfbab8e0, receiver=0x95a9458, event=0xbfbab594) at ../../kdeui/kernel/kapplication.cpp:302
#18 0xb589d6cb in QCoreApplication::notifyInternal (this=0xbfbab8e0, receiver=0x95a9458, event=0xbfbab594) at kernel/qcoreapplication.cpp:610
#19 0xb58c82ca in QCoreApplication::sendEvent (source=0x9418458) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 socketNotifierSourceDispatch (source=0x9418458) at kernel/qeventdispatcher_glib.cpp:110
#21 0xb5023e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#22 0xb5027730 in ?? () from /lib/libglib-2.0.so.0
#23 0xb5027863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#24 0xb58c802c in QEventDispatcherGlib::processEvents (this=0x93f7cc8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#25 0xb5e12be5 in QGuiEventDispatcherGlib::processEvents (this=0x93f7cc8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#26 0xb589bc79 in QEventLoop::processEvents (this=0xbfbab834, flags=) at kernel/qeventloop.cpp:149
#27 0xb589c0ca in QEventLoop::exec (this=0xbfbab834, flags=...) at kernel/qeventloop.cpp:201
#28 0xb589e53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#29 0xb5d71dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#30 0x081ee3f3 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-15 23:37:07 UTC
Fixed in KDE SC 4.4.1 and 4.5
Regards

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