Bug 92554 - Kopete crashed if I use SSL for IRC
Summary: Kopete crashed if I use SSL for IRC
Status: RESOLVED DUPLICATE of bug 90212
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.9.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-11-02 00:50 UTC by Giovanni Venturi
Modified: 2004-11-02 20:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Giovanni Venturi 2004-11-02 00:50:15 UTC
Version:           0.9.1 (using KDE 3.3.1, compiled sources)
Compiler:          gcc version 3.3.4
OS:                Linux (i686) release 2.6.9-ac6

I enabled SSL for an IRC account and Kopete crashed:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3939)]
[New Thread 32769 (LWP 3948)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3939)]
[New Thread 32769 (LWP 3948)]
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 3939)]
[New Thread 32769 (LWP 3948)]
[New Thread 81923 (LWP 3955)]
[New Thread 49156 (LWP 3951)]
[KCrash handler]
#6  0x4268a9d4 in X509_get_subject_name () from /usr/lib/./libcrypto.so.0
#7  0x409fc768 in KOpenSSLProxy::X509_get_subject_name (this=0x829bd78, a=0x0)
    at kopenssl.cc:832
#8  0x409eb1c1 in KSSLCertificate::getSubject (this=0x850a358)
    at ksslcertificate.cc:170
#9  0x409f1a34 in KSSLPeerInfo::certMatchesAddress (this=0x850a358)
    at ksslpeerinfo.cc:67
#10 0x42954e8b in KSSLSocket::verifyCertificate (this=0x85401e8)
    at ksslsocket.cpp:263
#11 0x429542f5 in KSSLSocket::slotConnected (this=0x85401e8)
    at ksslsocket.cpp:149
#12 0x42956345 in KSSLSocket::qt_invoke (this=0x85401e8, _id=7, _o=0xbfffef20)
    at ksslsocket.moc:96
#13 0x4149a777 in QObject::activate_signal ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#14 0x4149a62c in QObject::activate_signal ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#15 0x410d1211 in KExtendedSocket::connectionSuccess (this=0x85401e8)
    at kextsock.moc:112
#16 0x410cfd6f in KExtendedSocket::connectionEvent (this=0x85401e8)
    at kextsock.cpp:1811
#17 0x410cf91d in KExtendedSocket::socketActivityWrite (this=0x85401e8)
    at kextsock.cpp:1729
#18 0x410d1306 in KExtendedSocket::qt_invoke (this=0x85401e8, _id=3, 
    _o=0xbffff110) at kextsock.moc:131
#19 0x4295637b in KSSLSocket::qt_invoke (this=0x85401e8, _id=3, _o=0xbffff110)
    at ksslsocket.moc:100
#20 0x4149a803 in QObject::activate_signal ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#21 0x4149a93c in QObject::activate_signal ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#22 0x417bdfa8 in QSocketNotifier::activated ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#23 0x414b56ed in QSocketNotifier::event ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#24 0x4143ff8d in QApplication::internalNotify ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#25 0x4143f56d in QApplication::notify ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#26 0x40ffd66e in KApplication::notify (this=0xbffff6a0, receiver=0x851a6c8, 
    event=0xbffff420) at kapplication.cpp:495
#27 0x4142f77e in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#28 0x413ebc69 in QEventLoop::processEvents ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#29 0x414514eb in QEventLoop::enterLoop ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#30 0x41451394 in QEventLoop::exec () from /usr/lib/qt-copy/lib/libqt-mt.so.3
#31 0x414401e0 in QApplication::exec ()
   from /usr/lib/qt-copy/lib/libqt-mt.so.3
#32 0x0806e503 in main (argc=7, argv=0xbffff834) at main.cpp:100
Comment 1 Michel Hermier 2004-11-02 20:08:14 UTC

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