[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    KIO is blocking
From:       Paulo Moura Guedes <moura () kdewebdev ! org>
Date:       2007-03-28 0:34:53
Message-ID: 200703280134.53747.moura () kdewebdev ! org
[Download RAW message or body]

Hi,

My application hangs, always with this bt:

#0  0xffffe410 in __kernel_vsyscall ()
#1  0xb7e09543 in __read_nocancel () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb7783794 in KIO::Connection::read (this=0x8772ff0, _cmd=0xbfc9fcbc, 
data=@0xbfc9fcb8) at /home/kde/trunk/KDE/kdelibs/kio/kio/connection.cpp:249
#3  0xb7774139 in KIO::SlaveInterface::dispatch (this=0x8772fb0) 
at /home/kde/trunk/KDE/kdelibs/kio/kio/slaveinterface.cpp:149
#4  0xb7771e24 in KIO::Slave::gotInput (this=0x8772fb0) 
at /home/kde/trunk/KDE/kdelibs/kio/kio/slave.cpp:229
#5  0xb7772366 in KIO::Slave::qt_metacall (this=0x8772fb0, 
_c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfca01a0) at slave.moc:74
#6  0xb7f13bcc in QMetaObject::activate (sender=0x885caa0, 
from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3037
#7  0xb7f13dc8 in QMetaObject::activate (sender=0x885caa0, m=0xb7f859f8, 
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3083
#8  0xb7f38713 in QIODevice::readyRead (this=0x885caa0) 
at .moc/debug-shared/moc_qiodevice.cpp:79
#9  0xb7d81c5d in KNetwork::KClientSocketBase::slotReadActivity 
(this=0x885caa0) 
at /home/kde/trunk/KDE/kdelibs/kdecore/network/kclientsocketbase.cpp:386
#10 0xb7d8283c in KNetwork::KClientSocketBase::qt_metacall (this=0x885caa0, 
_c=QMetaObject::InvokeMetaMethod, _id=8, _a=0xbfca078c)
    at kclientsocketbase.moc:90
#11 0xb7d96b3c in KNetwork::KStreamSocket::qt_metacall (this=0x885caa0, 
_c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbfca078c) at 
kstreamsocket.moc:66
#12 0xb7f13bcc in QMetaObject::activate (sender=0x885a938, 
from_signal_index=4, to_signal_index=4, argv=0xbfca078c) at 
kernel/qobject.cpp:3037
#13 0xb7f13dc8 in QMetaObject::activate (sender=0x885a938, m=0xb7f85ae8, 
local_signal_index=0, argv=0xbfca078c) at kernel/qobject.cpp:3083
#14 0xb7f3a4b0 in QSocketNotifier::activated (this=0x885a938, _t1=15) 
at .moc/debug-shared/moc_qsocketnotifier.cpp:80
#15 0xb7f1eb09 in QSocketNotifier::event (this=0x885a938, e=0xbfca0cd8) at 
kernel/qsocketnotifier.cpp:304
#16 0xb693d7b5 in QApplicationPrivate::notify_helper (this=0x8068280, 
receiver=0x885a938, e=0xbfca0cd8) at kernel/qapplication.cpp:3468
#17 0xb693dac5 in QApplication::notify (this=0xbfca0f44, receiver=0x885a938, 
e=0xbfca0cd8) at kernel/qapplication.cpp:3043
#18 0xb7ad59b2 in KApplication::notify (this=0xbfca0f44, receiver=0x885a938, 
event=0xbfca0cd8)
    at /home/kde/trunk/KDE/kdelibs/kdeui/kernel/kapplication.cpp:299
#19 0xb7f00cda in QCoreApplication::notifyInternal (this=0xbfca0f44, 
receiver=0x885a938, event=0xbfca0cd8) at kernel/qcoreapplication.cpp:506
#20 0xb7f049bb in QCoreApplication::sendEvent (receiver=0x885a938, 
event=0xbfca0cd8) at qcoreapplication.h:186
#21 0xb7f2bb85 in socketNotifierSourceDispatch (source=0x8074590) at 
kernel/qeventdispatcher_glib.cpp:89
#22 0xb64c78d6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb64ca996 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#24 0xb64cae1e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb7f2ba00 in QEventDispatcherGlib::processEvents (this=0x80727d0, 
flags=@0xbfca0e28) at kernel/qeventdispatcher_glib.cpp:323
#26 0xb69d17be in QGuiEventDispatcherGlib::processEvents (this=0x80727d0, 
flags=@0xbfca0e5c) at kernel/qguieventdispatcher_glib.cpp:178
#27 0xb7effba0 in QEventLoop::processEvents (this=0xbfca0ed0, 
flags=@0xbfca0e94) at kernel/qeventloop.cpp:126
#28 0xb7effe04 in QEventLoop::exec (this=0xbfca0ed0, flags=@0xbfca0ed8) at 
kernel/qeventloop.cpp:168
#29 0xb7f04797 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:724
#30 0xb693cc60 in QApplication::exec () at kernel/qapplication.cpp:2983
#31 0x0804fd9d in main (argc=1, argv=0xbfca1014) 
at /home/kde/trunk/KDE/kdewebdev/klinkstatus/src/main.cpp:95

This started to happen some days ago, after updating trunk, don't know exactly 
when.
Does anybody have some idea what change could cause this behavior?

Paulo
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]