ktorrent crashes with SIGABRT

Bug #81568 reported by Timothy Miller
8
Affects Status Importance Assigned to Milestone
ktorrent (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

KTorrent crashed with SIGABRT. Here's the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232959808 (LWP 9014)]
[New Thread -1245033552 (LWP 9042)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb687a9a1 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb687c2b9 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb68ae87a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#10 0xb68b4fd4 in malloc_usable_size () from /lib/tls/i686/cmov/libc.so.6
#11 0xb68b534a in free () from /lib/tls/i686/cmov/libc.so.6
#12 0xb6a558b1 in operator delete () from /usr/lib/libstdc++.so.6
#13 0xb7f4624a in QValueListPrivate<bt::Request>::remove ()
   from /usr/lib/libktorrent.so.0
#14 0xb7f04e2d in bt::PeerDownloader::choked () from /usr/lib/libktorrent.so.0
#15 0xb7f11a71 in bt::Peer::packetReady () from /usr/lib/libktorrent.so.0
#16 0xb7f11ee6 in bt::PacketReader::update () from /usr/lib/libktorrent.so.0
#17 0xb7f11f86 in bt::Peer::update () from /usr/lib/libktorrent.so.0
#18 0xb7f35f68 in bt::PeerManager::update () from /usr/lib/libktorrent.so.0
#19 0xb7f3b354 in bt::TorrentControl::update () from /usr/lib/libktorrent.so.0
#20 0x08061fd5 in ?? ()
#21 0x0806efec in ?? ()
#22 0xb7049051 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#23 0xb7049aec in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#24 0xb73de536 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#25 0xb706e049 in QTimer::event () from /usr/lib/libqt-mt.so.3
#26 0xb6fdef3e in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#27 0xb6fdf13a in QApplication::notify () from /usr/lib/libqt-mt.so.3
#28 0xb7763d7d in KApplication::notify () from /usr/lib/libkdecore.so.4
#29 0xb6f70157 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#30 0xb6fd092b in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#31 0xb6f83f67 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#32 0xb6ff7a2f in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#33 0xb6ff7952 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#34 0xb6fdda4d in QApplication::exec () from /usr/lib/libqt-mt.so.3
#35 0x08064e5a in ?? ()
#36 0xb6866ea2 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x0805e261 in ?? ()

Revision history for this message
John Dong (jdong) wrote :

Thanks for your bug report.

What version of KTorrent are you using? This backtrace looks vaguely familiar to a bug in 2.0.1 that has been fixed in later releases.

The Backports repository and also ktorrent.org's homepage can supply Edgy and Dapper with 2.0.3 packages.

Changed in ktorrent:
status: Unconfirmed → Needs Info
Revision history for this message
Timothy Miller (theosib) wrote :

Thank you for looking into this problem.

I'm using version 2.0.3, which appears to be the latest with Dapper.

Revision history for this message
John Dong (jdong) wrote :

Well... wonderfully lovely.... </sarcasm>

Is trying a 2.1 RC1 package an option for you (I have prepared Dapper and Edgy packages on ktorrent.org's download page. If you look inside KTorrent's forum's Development section you can even find links to up-to-the-day SVN debs).

I'd really appreciate it if you can see if this problem happens with the 2.1 series, as that is clearly the future :)

Revision history for this message
Timothy Miller (theosib) wrote :

I certainly don't mind testing a different version. It's just that I haven't been able to reproduce the problem. I restarted KTorrent, and it continued where it left off (finally, something that handles crashes well!!!!), and has been stable ever since.

Sorry. :/

Revision history for this message
Rich Johnson (nixternal) wrote :

I am closing this report since the original poster cannot recreate the crash. If you run back into this problem I urge you to reopen this report as well as provide information to see if someone else can recreate the issue as well and confirm. Thank you!

Changed in ktorrent:
status: Needs Info → Rejected
Revision history for this message
sapran (sapran) wrote :
Download full text (4.1 KiB)

I am experiencing a similar problem after upgrading to 2.2.4 today.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1235138880 (LWP 2831)]
[KCrash handler]
#6 0xffffe410 in __kernel_vsyscall ()
#7 0xb666f875 in raise () from /lib/tls/i686/cmov/libc.so.6
#8 0xb6671201 in abort () from /lib/tls/i686/cmov/libc.so.6
#9 0xb6234dbc in sockaddr2sockshost () from /usr/lib/libdsocksd.so.0
#10 0xb622b051 in udpsetup () from /usr/lib/libdsocksd.so.0
#11 0xb622bbac in Rsendto () from /usr/lib/libdsocksd.so.0
#12 0xb752b4a8 in KSocks::sendto () from /usr/lib/libkdecore.so.4
#13 0xb764d646 in KNetwork::KSocksSocketDevice::writeBlock ()
   from /usr/lib/libkdecore.so.4
#14 0xb7656065 in KNetwork::KClientSocketBase::writeBlock ()
   from /usr/lib/libkdecore.so.4
#15 0xb76560f6 in KNetwork::KDatagramSocket::writeBlock ()
   from /usr/lib/libkdecore.so.4
#16 0xb764a7b0 in KNetwork::KDatagramSocket::send ()
   from /usr/lib/libkdecore.so.4
#17 0xb7e9d8fb in dht::RPCServer::send () from /usr/lib/libktorrent-2.2.4.so
#18 0xb7e9d9b6 in dht::RPCServer::sendMsg ()
   from /usr/lib/libktorrent-2.2.4.so
#19 0xb7e9e234 in dht::RPCServer::doCall () from /usr/lib/libktorrent-2.2.4.so
#20 0xb7eacb94 in dht::Task::rpcCall () from /usr/lib/libktorrent-2.2.4.so
#21 0xb7eaf4d1 in dht::AnnounceTask::update ()
   from /usr/lib/libktorrent-2.2.4.so
#22 0xb7eacee5 in dht::Task::start () from /usr/lib/libktorrent-2.2.4.so
#23 0xb7ea2fba in dht::DHT::announce () from /usr/lib/libktorrent-2.2.4.so
#24 0xb7eb0fdc in dht::DHTTrackerBackend::doRequest ()
   from /usr/lib/libktorrent-2.2.4.so
#25 0xb7eb112a in dht::DHTTrackerBackend::start ()
   from /usr/lib/libktorrent-2.2.4.so
#26 0xb7e933b2 in bt::PeerSourceManager::start ()
   from /usr/lib/libktorrent-2.2.4.so
#27 0xb7e52656 in bt::TorrentControl::continueStart ()
   from /usr/lib/libktorrent-2.2.4.so
#28 0xb7e528db in bt::TorrentControl::start ()
   from /usr/lib/libktorrent-2.2.4.so
#29 0xb7e89235 in bt::QueueManager::startSafely ()
   from /usr/lib/libktorrent-2.2.4.so
#30 0xb7e89867 in bt::QueueManager::start ()
   from /usr/lib/libktorrent-2.2.4.so
#31 0x080781b9 in ?? ()
#32 0x0807e398 in ?? ()
#33 0x0807c522 in ?? ()
#34 0x08074390 in ?? ()
#35 0x08076df1 in ?? ()
#36 0xb75dc91f in KUniqueApplication::processDelayed ()
   from /usr/lib/libkdecore.so.4
#37 0xb75de3d8 in KUniqueApplication::qt_invoke ()
   from /usr/lib/libkdecore.so.4
#38 0x080767ef in ?? ()
#39 0xb6ebf893 in QObject::activate_signal () from /usr...

Read more...

Changed in ktorrent:
status: Invalid → Incomplete
status: Incomplete → New
Revision history for this message
Andreas Moog (ampelbein) wrote : Still an Issue?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Is this still an issue for you? Thanks in advance.

 status incomplete
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiwUjUACgkQ06FgkPZwicSYMQCfSK5Z5uF7w26sRADXFSKKTG3K
bEAAoO6qw+tqjaeUsP/TIg791+ccyKU5
=nzex
-----END PGP SIGNATURE-----

Changed in ktorrent:
status: New → Incomplete
Revision history for this message
sapran (sapran) wrote : Re: [Bug 81568] Still an Issue?

no, I moved from KDE...

sapran

On Sat, Aug 23, 2008 at 9:08 PM, Andreas Moog <email address hidden>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Is this still an issue for you? Thanks in advance.
>
> status incomplete
> subscribe
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkiwUjUACgkQ06FgkPZwicSYMQCfSK5Z5uF7w26sRADXFSKKTG3K
> bEAAoO6qw+tqjaeUsP/TIg791+ccyKU5
> =nzex
> -----END PGP SIGNATURE-----
>
> ** Changed in: ktorrent (Ubuntu)
> Status: New => Incomplete
>
> --
> ktorrent crashes with SIGABRT
> https://bugs.launchpad.net/bugs/81568
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Andreas Moog (ampelbein) wrote : Closing this Bug since there was no Information provided

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In that case, I'm closing this report.

 status invalid

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkiwYJUACgkQ06FgkPZwicSH0QCg4k+oOAewMBGYMzOCzCE6+kH2
V6oAoLIlYXOWkcRq6yQ4h9FfDt9Y+hMT
=UNXj
-----END PGP SIGNATURE-----

Changed in ktorrent:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.