Bug 187005

Summary: crash for unknown reason
Product: [I don't know] kde Reporter: E. Kastelijn <kde2>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description E. Kastelijn 2009-03-12 20:27:41 UTC
Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Fedora RPMs

Application: KDE Daemon (kded4), signal SIGSEGV
[?1034h[Thread debugging using libthread_db enabled]
0x00000031ccea7f50 in __nanosleep_nocancel () from /lib64/libc.so.6
Current language:  auto; currently c
[Current thread is 1 (Thread 0x7f38e81e7800 (LWP 21991))]

Thread 1 (Thread 0x7f38e81e7800 (LWP 21991)):
[KCrash Handler]
#5  QString::size () at ../../src/corelib/tools/qstring.h:100
#6  QString::operator== (this=<value optimized out>, other=@0x7ffff0235970) at tools/qstring.cpp:1768
#7  0x00000035dbb1e216 in KDirWatchPrivate::inotifyEventReceived (this=0xdcce00) at /usr/src/debug/kdelibs-4.2.0/kio/kio/kdirwatch.cpp:296
#8  0x00000035dbb20fd8 in KDirWatchPrivate::qt_metacall (this=0xdcce00, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff0236b90)
    at /usr/src/debug/kdelibs-4.2.0/x86_64-redhat-linux-gnu/kio/kdirwatch_p.moc:74
#9  0x0000003bd8556764 in QMetaObject::activate (sender=0xdcc9a0, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x770065006e002e) at kernel/qobject.cpp:3031
#10 0x0000003bd858cede in QSocketNotifier::activated (this=0x3400650064006b, _t1=10) at .moc/release-shared/moc_qsocketnotifier.cpp:81
#11 0x0000003bd855c273 in QSocketNotifier::event (this=0xdcc9a0, e=0x7ffff0237160) at kernel/qsocketnotifier.cpp:320
#12 0x00000035dab828dd in QApplicationPrivate::notify_helper (this=0xd355f0, receiver=0xdcc9a0, e=0x7ffff0237160) at kernel/qapplication.cpp:3803
#13 0x00000035dab8a68a in QApplication::notify (this=0x7ffff0237480, receiver=0xdcc9a0, e=0x7ffff0237160) at kernel/qapplication.cpp:3768
#14 0x00000035da404deb in KApplication::notify (this=0x7ffff0237480, receiver=0xdcc9a0, event=0x7ffff0237160) at /usr/src/debug/kdelibs-4.2.0/kdeui/kernel/kapplication.cpp:307
#15 0x0000003bd8542391 in QCoreApplication::notifyInternal (this=0x7ffff0237480, receiver=0xdcc9a0, event=0x7ffff0237160) at kernel/qcoreapplication.cpp:587
#16 0x0000003bd856aa19 in QCoreApplication::sendEvent () at ../../src/corelib/kernel/qcoreapplication.h:209
#17 socketNotifierSourceDispatch (source=0xd41680) at kernel/qeventdispatcher_glib.cpp:105
#18 0x0000003bd6c3779b in g_main_dispatch () at gmain.c:2144
#19 IA__g_main_context_dispatch (context=0xd40920) at gmain.c:2697
#20 0x0000003bd6c3af6d in g_main_context_iterate (context=0xd40920, block=1, dispatch=1, self=<value optimized out>) at gmain.c:2778
#21 0x0000003bd6c3b12b in IA__g_main_context_iteration (context=0xd40920, may_block=1) at gmain.c:2841
#22 0x0000003bd856a79f in QEventDispatcherGlib::processEvents (this=0xd3e260, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319
#23 0x00000035dac1328f in QGuiEventDispatcherGlib::processEvents (this=0x3400650064006b, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:198
#24 0x0000003bd8540cb2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:143
#25 0x0000003bd8540e3d in QEventLoop::exec (this=0x7ffff02373c0, flags=) at kernel/qeventloop.cpp:194
#26 0x0000003bd85432ed in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#27 0x00000035dc40b2e7 in kdemain (argc=1, argv=0x7ffff0237838) at /usr/src/debug/kdelibs-4.2.0/kded/kded.cpp:937
#28 0x00000031cce1e576 in __libc_start_main (main=0x4007d0 <main>, argc=1, ubp_av=0x7ffff0237838, init=0x400800 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7ffff0237828) at libc-start.c:220
#29 0x0000000000400709 in _start ()
Comment 1 Dario Andres 2009-03-12 20:56:24 UTC
Thanks for reporting

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