Bug 857611

Summary: [abrt] flush-0.9.10-7.fc17: Process /usr/bin/flush was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Max <glmakx>
Component: flushAssignee: Oxana Kurysheva <okurysheva>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: okurysheva
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:bb697ec9db4c69f3fbdba4e089be32a4f5d03894
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 06:23:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: core_backtrace
none
File: environ
none
File: limits
none
File: backtrace
none
File: cgroup
none
File: maps
none
File: dso_list
none
File: open_fds
none
File: var_log_messages none

Description Max 2012-09-15 05:56:49 UTC 
Version-Release number of selected component:
flush-0.9.10-7.fc17

Additional info:
libreport version: 2.0.13
abrt_version:   2.0.12
backtrace_rating: 4
cmdline:        flush /tmp/70C2BEE430B6E1B1BC713B0A9638682CDC7B5855.torrent
crash_function: libtorrent::throw_invalid_handle
kernel:         3.5.3-1.fc17.i686

truncated backtrace:
:Thread no. 1 (3 frames)
: #7 libtorrent::throw_invalid_handle at torrent_handle.cpp
: #8 libtorrent::torrent_handle::info_hash at torrent_handle.cpp
: #9 Torrent_id::Torrent_id at common.cpp
Comment 1 Max 2012-09-15 05:56:52 UTC 
Created attachment 613160 [details]
File: core_backtrace
Comment 2 Max 2012-09-15 05:56:54 UTC 
Created attachment 613161 [details]
File: environ
Comment 3 Max 2012-09-15 05:56:56 UTC 
Created attachment 613162 [details]
File: limits
Comment 4 Max 2012-09-15 05:56:58 UTC 
Created attachment 613163 [details]
File: backtrace
Comment 5 Max 2012-09-15 05:57:00 UTC 
Created attachment 613164 [details]
File: cgroup
Comment 6 Max 2012-09-15 05:57:03 UTC 
Created attachment 613165 [details]
File: maps
Comment 7 Max 2012-09-15 05:57:05 UTC 
Created attachment 613166 [details]
File: dso_list
Comment 8 Max 2012-09-15 05:57:07 UTC 
Created attachment 613167 [details]
File: open_fds
Comment 9 Max 2012-09-15 05:57:09 UTC 
Created attachment 613168 [details]
File: var_log_messages
Comment 10 Fedora End Of Life 2013-07-04 01:40:30 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

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 prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life.

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.
Comment 11 Fedora End Of Life 2013-08-01 06:23:44 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.

Thank you for reporting this bug and we are sorry it could not be fixed.