Bug 170629 - Random crashes due to inotify
Summary: Random crashes due to inotify
Status: RESOLVED DUPLICATE of bug 165548
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kded (show other bugs)
Version: 4.1
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-07 17:43 UTC by Jeff Mitchell
Modified: 2008-10-20 13:58 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 Jeff Mitchell 2008-09-07 17:43:39 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Crash handler just pops up sometimes, saying the kded daemon crashed.

Here's a backtrace. Looks like it's due to the inotify code in kdirwatch.

Application: KDE Daemon (kded4), signal SIGSEGV
Using host libthread_db library "/lib/libthread_db.so.1".

Thread 1 (Thread 0xb62376d0 (LWP 4220)):
[KCrash Handler]
#6  0xb7558ece in QString::size (this=0x89bea68) at ../../include/QtCore/../../src/corelib/tools/qstring.h:106
#7  0xb758823b in QString::operator== (this=0x89bea68, other=@0xbfe27fa0) at tools/qstring.cpp:1769
#8  0xb7daca8e in KDirWatchPrivate::inotifyEventReceived (this=0x896c318) at /home/jeff/kde4svn/src/KDE/kdelibs/kio/kio/kdirwatch.cpp:290
#9  0xb7dad171 in KDirWatchPrivate::qt_metacall (this=0x896c318, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe2810c) at /home/jeff/kde4svn/build/KDE/kdelibs/kio/kdirwatch_p.moc:74
#10 0xb7647849 in QMetaObject::activate (sender=0x8966048, from_signal_index=4, to_signal_index=4, argv=0xbfe2810c) at kernel/qobject.cpp:3013
#11 0xb7647ccb in QMetaObject::activate (sender=0x8966048, m=0xb76e3890, local_signal_index=0, argv=0xbfe2810c) at kernel/qobject.cpp:3086
#12 0xb7688894 in QSocketNotifier::activated (this=0x8966048, _t1=10) at .moc/debug-shared/moc_qsocketnotifier.cpp:81
#13 0xb7651001 in QSocketNotifier::event (this=0x8966048, e=0xbfe285fc) at kernel/qsocketnotifier.cpp:326
#14 0xb6af694d in QApplicationPrivate::notify_helper (this=0x88eca80, receiver=0x8966048, e=0xbfe285fc) at kernel/qapplication.cpp:3800
#15 0xb6af6c66 in QApplication::notify (this=0xbfe28a38, receiver=0x8966048, e=0xbfe285fc) at kernel/qapplication.cpp:3392
#16 0xb7b137b3 in KApplication::notify (this=0xbfe28a38, receiver=0x8966048, event=0xbfe285fc) at /home/jeff/kde4svn/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:311
#17 0xb7632af2 in QCoreApplication::notifyInternal (this=0xbfe28a38, receiver=0x8966048, event=0xbfe285fc) at kernel/qcoreapplication.cpp:587
#18 0xb763666d in QCoreApplication::sendEvent (receiver=0x8966048, event=0xbfe285fc) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 0xb7663c87 in QEventDispatcherUNIX::activateSocketNotifiers (this=0x88ee250) at kernel/qeventdispatcher_unix.cpp:853
#20 0xb7665db2 in QEventDispatcherUNIXPrivate::doSelect (this=0x88efeb0, flags=@0xbfe2878c, timeout=0xbfe2877c) at kernel/qeventdispatcher_unix.cpp:252
#21 0xb7665f58 in QEventDispatcherUNIX::processEvents (this=0x88ee250, flags=@0xbfe288ac) at kernel/qeventdispatcher_unix.cpp:895
#22 0xb6b9f197 in QEventDispatcherX11::processEvents (this=0x88ee250, flags=@0xbfe288e8) at kernel/qeventdispatcher_x11.cpp:154
#23 0xb762f9a6 in QEventLoop::processEvents (this=0xbfe28960, flags=@0xbfe28924) at kernel/qeventloop.cpp:149
#24 0xb762fbe5 in QEventLoop::exec (this=0xbfe28960, flags=@0xbfe28968) at kernel/qeventloop.cpp:196
#25 0xb76332db in QCoreApplication::exec () at kernel/qcoreapplication.cpp:849
#26 0xb6af6666 in QApplication::exec () at kernel/qapplication.cpp:3330
#27 0xb7f06687 in kdemain (argc=1, argv=0xbfe28bc4) at /home/jeff/kde4svn/src/KDE/kdelibs/kded/kded.cpp:896
#28 0x080486e6 in main (argc=1, argv=0x36) at /home/jeff/kde4svn/build/KDE/kdelibs/kded/kded4_dummy.cpp:3
Comment 1 Frank Reininghaus 2008-10-15 19:30:52 UTC
Might be a duplicate of bug 165548 (that crash occurs while updating packages).
Comment 2 David Faure 2008-10-20 13:58:54 UTC

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