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

List:       kopete-devel
Subject:    [kopete-devel] stuck in msn, can't get out
From:       Grzegorz Piotr Jaskiewicz <gj () kde ! org ! uk>
Date:       2005-05-22 19:20:09
Message-ID: 4290DB69.5010603 () kde ! org ! uk
[Download RAW message or body]

Hi list

Well, no whining this time :-)

I decided to try to "connect all" on my 20 and some accounts. Including
one MSN, there are one of each, two jabbers and some gadus (I guess
therez 16 of them, but I'm too lazy to count). Anyways, it got stucked.
I decided after 10 minutes to issue killall -SIGSEGV kopete, and herez
the output:

Using host libthread_db library "/lib/tls/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1241729344 (LWP 19099)]
[New Thread -1270228048 (LWP 19152)]
[New Thread -1287078992 (LWP 19151)]
[New Thread -1247102032 (LWP 19150)]
[New Thread -1255490640 (LWP 19149)]
[New Thread -1278616656 (LWP 19148)]
[New Thread -1295467600 (LWP 19147)]
[KCrash handler]
#3  0xb626d121 in pthread_cond_wait@@GLIBC_2.3.2 ()
   from /lib/tls/libpthread.so.0
#4  0xb6b6624e in QWaitCondition::wait (this=0x86a6fb8, mutex=0x85ae8dc,
    time=4294967295) at tools/qwaitcondition_unix.cpp:303
#5  0xb7020fbf in KNetwork::KResolver::wait (this=0x84c817c, msec=0)
    at /home/gj/kde-sources/kdelibs/kdecore/network/kresolver.cpp:487
#6  0xb6fc5410 in KExtendedSocket::lookup (this=0x877d8f8)
    at /home/gj/kde-sources/kdelibs/kdecore/kextsock.cpp:749
#7  0xb4a8c16f in SslLoginHandler::sendHttpRequest (this=0x87c0f18,
port=443)
    at
/home/gj/kde-sources/kdenetwork/kopete/protocols/msn/sslloginhandler.cpp:378
#8  0xb4a8c8c1 in SslLoginHandler::sendLoginServerRequest (this=0x87c0f18)
    at
/home/gj/kde-sources/kdenetwork/kopete/protocols/msn/sslloginhandler.cpp:419
#9  0xb4a8e5be in SslLoginHandler::login (this=0x87c0f18)
    at
/home/gj/kde-sources/kdenetwork/kopete/protocols/msn/sslloginhandler.cpp:157
#10 0xb4a62ffc in MSNNotifySocket::parseCommand (this=0x87895c0,
    cmd=@0xbfffecf0, id=2, data=@0xbfffedd0) at qstring.h:860
#11 0xb4a4e321 in MSNSocket::parseLine (this=0x87895c0, str=@0xbfffee60)
    at
/home/gj/kde-sources/kdenetwork/kopete/protocols/msn/msnsocket.cpp:332
#12 0xb4a52794 in MSNSocket::slotReadLine (this=0x87895c0)
    at
/home/gj/kde-sources/kdenetwork/kopete/protocols/msn/msnsocket.cpp:260
#13 0xb4a5310e in MSNSocket::slotDataReceived (this=0x87895c0)
    at
/home/gj/kde-sources/kdenetwork/kopete/protocols/msn/msnsocket.cpp:221
#14 0xb4a55ed8 in MSNSocket::qt_invoke (this=0x87895c0, _id=9,
_o=0xbffff1b0)
    at msnsocket.moc:220
#15 0xb4a6217c in MSNNotifySocket::qt_invoke (this=0x87895c0, _id=9,
    _o=0xbffff1b0) at msnnotifysocket.moc:394
#16 0xb68a5e7b in QObject::activate_signal (this=0x87adc28,
clist=0x812fe80,
    o=0xbffff1b0) at kernel/qobject.cpp:2355
#17 0xb68a5d1d in QObject::activate_signal (this=0x87adc28, signal=9)
    at kernel/qobject.cpp:2324
#18 0xb702e5d9 in KNetwork::KClientSocketBase::readyRead (this=0x87adc28)
    at qmetaobject.h:261
#19 0xb702e619 in KNetwork::KClientSocketBase::slotReadActivity (this=0x7)
    at
/home/gj/kde-sources/kdelibs/kdecore/network/kclientsocketbase.cpp:416
#20 0xb7036569 in KNetwork::KBufferedSocket::slotReadActivity
(this=0x87adc28)
    at /home/gj/kde-sources/kdelibs/kdecore/network/kbufferedsocket.cpp:342
#21 0xb7036a2c in KNetwork::KBufferedSocket::qt_invoke (this=0x87adc28,
    _id=8, _o=0xbffff300) at kbufferedsocket.moc:97
#22 0xb68a5e7b in QObject::activate_signal (this=0x86e5d68,
clist=0x8752b80,
    o=0xbffff300) at kernel/qobject.cpp:2355
#23 0xb68a61d4 in QObject::activate_signal (this=0x86e5d68, signal=2,
    param=18) at kernel/qobject.cpp:2448
#24 0xb6c0bfcd in QSocketNotifier::activated (this=0x86e5d68, t0=18)
    at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#25 0xb68c6c98 in QSocketNotifier::event (this=0x86e5d68, e=0xbffff600)
    at kernel/qsocketnotifier.cpp:258
#26 0xb68414fd in QApplication::internalNotify (this=0xbffff8a0,
    receiver=0x86e5d68, e=0xbffff600) at kernel/qapplication.cpp:2635
#27 0xb68409c1 in QApplication::notify (this=0xbffff8a0,
receiver=0x86e5d68,
    e=0xbffff600) at kernel/qapplication.cpp:2358
#28 0xb6ec9eb3 in KApplication::notify (this=0xbffff8a0,
receiver=0x86e5d68,
    event=0xbffff600)
    at /home/gj/kde-sources/kdelibs/kdecore/kapplication.cpp:549
#29 0xb67d2945 in QApplication::sendEvent (receiver=0x86e5d68,
    event=0xbffff600) at qapplication.h:491
#30 0xb682f3f7 in QEventLoop::activateSocketNotifiers (this=0x8141320)
    at kernel/qeventloop_unix.cpp:578
#31 0xb67e65e4 in QEventLoop::processEvents (this=0x8141320, flags=4)
    at kernel/qeventloop_x11.cpp:383
#32 0xb6856588 in QEventLoop::enterLoop (this=0x8141320)
    at kernel/qeventloop.cpp:198
#33 0xb68564a6 in QEventLoop::exec (this=0x8141320)
    at kernel/qeventloop.cpp:145
#34 0xb684167d in QApplication::exec (this=0xbffff8a0)
    at kernel/qapplication.cpp:2758
#35 0x0806c163 in main (argc=7, argv=0xbffffa74)
    at /home/gj/kde-sources/kdenetwork/kopete/kopete/main.cpp:99


It clearly shows msn/ssl/kde sockets as the point of gridlock. If
someone would like to poke around and at least try to find the reason it
would be great. If you read this, you're really a great. Hope it wasn't
too much whining here this time.

Thanks.

-- 
GJ
_______________________________________________
kopete-devel mailing list
kopete-devel@kde.org
https://mail.kde.org/mailman/listinfo/kopete-devel
[prev in list] [next in list] [prev in thread] [next in thread]