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

Ktorrent 2.1.3 crash after data integrity check

Tags: None
(comma "," separated)
madberry
Registered Member
Posts
32
Karma
0
I was hoping this issue was fixed in the 2.1.3 version as well but ktorrent just crashed after checking the data of a torrent file here is the Backtrace for it....

Code: Select all
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1235056976 (LWP 17851)]
[New Thread -1262523488 (LWP 18420)]
[New Thread -1254130784 (LWP 18419)]
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb6680770 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6681ef3 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb6870520 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb686df55 in std::set_unexpected () from /usr/lib/libstdc++.so.6
#11 0xb686df92 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb686e0ca in __cxa_throw () from /usr/lib/libstdc++.so.6
#13 0xb7d7876f in bt::ChunkManager::saveIndexFile ()
   from /usr/lib/libktorrent-2.1.3.so
#14 0xb7d79f5e in bt::ChunkManager::dataChecked ()
   from /usr/lib/libktorrent-2.1.3.so
#15 0xb7d8c73a in bt::TorrentControl::afterDataCheck ()
   from /usr/lib/libktorrent-2.1.3.so
#16 0x080791ee in KTorrentCore::update ()
#17 0x0807bd42 in KTorrentCore::qt_invoke ()
#18 0xb6e40957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb6e413fc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb71cf00a in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#21 0xb6e68662 in QTimer::event () from /usr/lib/libqt-mt.so.3
#22 0xb6dd7b88 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#23 0xb6dd99b7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#24 0xb757bc82 in KApplication::notify () from /usr/lib/libkdecore.so.4
#25 0xb6d6a389 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#26 0xb6dca5d3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#27 0xb6d7eec5 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb6df225e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb6df206e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0xb6dd9731 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x08064057 in main ()
George
Moderator
Posts
5421
Karma
1

Tue Apr 10, 2007 5:29 pm
Hmm, an uncaught exception, easy to fix.
George
Moderator
Posts
5421
Karma
1

Tue Apr 10, 2007 6:00 pm
OK, should be fixed in latest SVN
madberry
Registered Member
Posts
32
Karma
0

Crashed again this time on.....

Wed Apr 11, 2007 4:01 am
Crashed again this time on recreating a file
Code: Select all
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1234794832 (LWP 21197)]
[New Thread -1262306400 (LWP 21250)]
[New Thread -1253913696 (LWP 21249)]
[KCrash handler]
#6  0x080791a5 in KTorrentCore::update ()
#7  0x0807bd42 in KTorrentCore::qt_invoke ()
#8  0xb6e80957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9  0xb6e813fc in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0xb720f00a in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#11 0xb6ea8662 in QTimer::event () from /usr/lib/libqt-mt.so.3
#12 0xb6e17b88 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#13 0xb6e199b7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#14 0xb75bbc82 in KApplication::notify () from /usr/lib/libkdecore.so.4
#15 0xb6daa389 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#16 0xb6e0a5d3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#17 0xb6dbeec5 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#18 0xb6e3225e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#19 0xb6e3206e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#20 0xb6e19731 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#21 0x08064057 in main ()



Is this the same exception?
George
Moderator
Posts
5421
Karma
1

Wed Apr 11, 2007 4:35 pm
Seems to be something else, could you recompile with debugging information turned on ? This should result in more usefull backtraces :

./configure --enable-debug=full
make
make install
madberry
Registered Member
Posts
32
Karma
0

Wed Apr 11, 2007 9:23 pm
Ok compiling with debugging right now


Bookmarks



Who is online

Registered users: Bing [Bot], Google [Bot], q.ignora, watchstar