Bug 691861 - [abrt] rtorrent-0.8.7-4.fc14: do_panic: Process /usr/bin/rtorrent was killed by signal 6 (SIGABRT)
Summary: [abrt] rtorrent-0.8.7-4.fc14: do_panic: Process /usr/bin/rtorrent was killed ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: rtorrent
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Conrad Meyer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:15d8ac5dba12687d64fbfdb6bff...
: 708243 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-29 17:13 UTC by Kiril Aleksandrov
Modified: 2011-10-28 05:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-28 05:28:25 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (11.01 KB, text/plain)
2011-03-29 17:13 UTC, Kiril Aleksandrov
no flags Details

Description Kiril Aleksandrov 2011-03-29 17:13:20 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 11279 bytes
cmdline: rtorrent
component: rtorrent
Attached file: coredump, 20455424 bytes
crash_function: do_panic
executable: /usr/bin/rtorrent
kernel: 2.6.35.11-83.fc14.x86_64
package: rtorrent-0.8.7-4.fc14
rating: 4
reason: Process /usr/bin/rtorrent was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1301418157
uid: 500

How to reproduce
-----
1. Try to restart a torrent.
2. Crash.

Comment 1 Kiril Aleksandrov 2011-03-29 17:13:23 UTC
Created attachment 488505 [details]
File: backtrace

Comment 2 Conrad Meyer 2011-10-28 01:16:19 UTC
*** Bug 708243 has been marked as a duplicate of this bug. ***

Comment 3 Conrad Meyer 2011-10-28 01:17:28 UTC
Both this bug and the bug I marked a dup look like rtorrent is using illegal instructions on your respective CPUs, OR has buggy assembly code.

Comment 4 Conrad Meyer 2011-10-28 05:28:25 UTC
But anyways, the solution is to file upstream. I can't glean anything useful from
these stack traces. wontfix.


Note You need to log in before you can comment on or make changes to this bug.