Red Hat Bugzilla – Bug 1011304
[abrt] rtorrent-0.9.3-5.fc19: handle_sigbus: Process /usr/bin/rtorrent was killed by signal 6 (SIGABRT)
Last modified: 2015-02-18 06:29:44 EST
Version-Release number of selected component:
runlevel: N 5
var_log_messages: Sep 24 09:07:35 netbook abrt: Saved core dump of pid 7880 (/usr/bin/rtorrent) to /var/tmp/abrt/ccpp-2013-09-24-09:07:33-7880 (60207104 bytes)
Thread no. 1 (10 frames)
#3 handle_sigbus at main.cc:949
#5 __bzero_sse2_rep at ../sysdeps/i386/i686/multiarch/memset-sse2-rep.S:746
#6 memcpy at /usr/include/bits/string3.h:51
#7 torrent::Chunk::from_buffer at chunk.cc:240
#8 torrent::PeerConnectionBase::down_chunk_process at peer_connection_base.cc:587
#9 torrent::PeerConnectionBase::down_chunk_from_buffer at peer_connection_base.cc:529
#10 read_message at peer_connection_leech.cc:296
#11 torrent::PeerConnection<(torrent::Download::ConnectionType)0>::event_read at peer_connection_leech.cc:390
#12 torrent::PollEPoll::perform at poll_epoll.cc:180
#13 torrent::PollEPoll::do_poll at poll_epoll.cc:210
Created attachment 802011 [details]
Created attachment 802012 [details]
Created attachment 802013 [details]
Created attachment 802014 [details]
Created attachment 802015 [details]
Created attachment 802016 [details]
Created attachment 802017 [details]
Created attachment 802018 [details]
Created attachment 802019 [details]
Is this reproducible, or did it just happen randomly?
Usually this just means the file backing an mmap(2) disappeared. Not much rtorrent can do about it, given the mmap() API. I think upstream was working on some hack to scan the set of open files to see which disappeared on it ... neat idea, not sure it is implemented yet.
rtorrent's entire trac appears to have gone missing, but this dates back a long time:
http://libtorrent.rakshasa.no/ticket/10 (archive: http://web.archive.org/web/20111104015334/http://libtorrent.rakshasa.no/ticket/10 )
And a bunch of newer bugs, although browsing trac is hard because the bugs have gone missing...
*** Bug 1015832 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.