Bug 603513 - [abrt] crash in par2cmdline-0.4.tbb.20100203-1.fc13: __TBB_rel_acq_fence: Process /usr/bin/par2 was killed by signal 4 (SIGILL)
Summary: [abrt] crash in par2cmdline-0.4.tbb.20100203-1.fc13: __TBB_rel_acq_fence: Pro...
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: par2cmdline
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Erik van Pienbroek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:184d58c2f1385eccfdb57735088...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-13 16:48 UTC by Alexandre Dutriaux
Modified: 2010-07-04 14:10 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-07-04 14:10:46 UTC


Attachments (Terms of Use)
File: backtrace (50.45 KB, text/plain)
2010-06-13 16:48 UTC, Alexandre Dutriaux
no flags Details

Description Alexandre Dutriaux 2010-06-13 16:48:55 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/par2 r -- '/home/adutriaux/.local/share/hellanzb/nzb/daemon.processing/ktr.sr.e21.oily.masturbation /ktr.sr.e21.oily.masturbation.par2' *._hellanzb_dupe*
comment: before migrating to fedora 13, I was working with fedora 12, and the couple hellanzb / par2cmdline works fine. 
component: par2cmdline
crash_function: __TBB_rel_acq_fence
executable: /usr/bin/par2
global_uuid: 184d58c2f1385eccfdb577350882e20b9b2942ab
kernel: 2.6.33.5-112.fc13.i686
package: par2cmdline-0.4.tbb.20100203-1.fc13
rating: 4
reason: Process /usr/bin/par2 was killed by signal 4 (SIGILL)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. get something through newsgroups, with hellanzb
2. when download is over, par2cmdline should be launched, and it chrash at this time

Comment 1 Alexandre Dutriaux 2010-06-13 16:48:58 UTC
Created attachment 423651 [details]
File: backtrace

Comment 2 Erik van Pienbroek 2010-07-04 14:10:46 UTC
This problem should be fixed already as of tbb-2.2-2.20090809.fc13


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