This forum has been archived. All content is frozen. Please use KDE Discuss instead.

Crash in KTorrent 2.1beta1

Tags: None
(comma "," separated)
theentity
Registered Member
Posts
2
Karma
0

Crash in KTorrent 2.1beta1

Tue Jan 02, 2007 11:16 am
hello I got this backtrace from a crash while ktorrent was seeding 4 torrents sys is.

kde-3.5.4
Qt-3.3.5
linux-2.6.20rc2
X86_64

here is my configure options. ./configure --prefix=/opt/kde --libdir=/opt/kde/lib64 --without-arts

This is the output from ktorrents crash as saved from debug window I ran backtrace.

Using host libthread_db library "/lib64/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47449116339296 (LWP 2385)]
[New Thread 1082141024 (LWP 2403)]
[KCrash handler]
#5 0x00002b27969a0615 in dht::ParseRsp () from /opt/kde/lib64/libktorrent.so.0
#6 0x00002b27969a07b0 in dht::MakeRPCMsg ()
from /opt/kde/lib64/libktorrent.so.0
#7 0x00002b27969952d3 in dht::RPCServer::readPacket ()
from /opt/kde/lib64/libktorrent.so.0
#8 0x00002b2796995540 in dht::RPCServer::qt_invoke ()
from /opt/kde/lib64/libktorrent.so.0
#9 0x00002b279886ebc8 in QObject::activate_signal ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#10 0x00002b279886f332 in QObject::activate_signal ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#11 0x00002b2797cb2cb5 in KNetwork::KClientSocketBase::qt_invoke ()
from /opt/kde/lib64/libkdecore.so.4
#12 0x00002b2797cb640a in KNetwork::KDatagramSocket::qt_invoke ()
from /opt/kde/lib64/libkdecore.so.4
#13 0x00002b279886ebc8 in QObject::activate_signal ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#14 0x00002b279886f1cf in QObject::activate_signal ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#15 0x00002b279888735b in QSocketNotifier::event ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#16 0x00002b2798815c6d in QApplication::internalNotify ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#17 0x00002b2798815e15 in QApplication::notify ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#18 0x00002b2797b89271 in KApplication::notify ()
from /opt/kde/lib64/libkdecore.so.4
#19 0x00002b279880ae1f in QEventLoop::activateSocketNotifiers ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#20 0x00002b27987cbbe8 in QEventLoop::processEvents ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#21 0x00002b2798829be5 in QEventLoop::enterLoop ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#22 0x00002b2798829b42 in QEventLoop::exec ()
from /usr/lib64/qt/lib/libqt-mt.so.3
#23 0x0000000000423270 in main ()
George
Moderator
Posts
5421
Karma
1

Tue Jan 02, 2007 6:25 pm
Does this happen frequently ? If so could you compile with debugging information (./configure --enable-debug=full), so that we can know the exact line number of the crash.


Bookmarks



Who is online

Registered users: bartoloni, Bing [Bot], Google [Bot], Yahoo [Bot]