Red Hat Bugzilla – Bug 969041
[abrt] par2cmdline-0.4.tbb.20100203-11.fc18: store: Process /usr/bin/par2 was killed by signal 11 (SIGSEGV)
Last modified: 2015-05-04 21:37:59 EDT
Description of problem:
git clone https://github.com/bup/bup.git
git checkout bup-0.24b
Version-Release number of selected component:
cmdline: par2 create -n1 -c200 -qq -- /home/alan/src/bup/buptest.tmp/objects/pack/pack-beb477b830f69b7d2271481796d5c7e82589019a /home/alan/src/bup/buptest.tmp/objects/pack/pack-beb477b830f69b7d2271481796d5c7e82589019a.pack /home/alan/src/bup/buptest.tmp/objects/pack/pack-beb477b830f69b7d2271481796d5c7e82589019a.idx
runlevel: N 5
Thread no. 1 (10 frames)
#0 store at ../../include/tbb/tbb_machine.h:625
#1 __TBB_store_relaxed<tbb::internal::task_proxy*, tbb::internal::task_proxy*> at ../../include/tbb/tbb_machine.h:676
#2 push at ../../src/tbb/mailbox.h:153
#3 prepare_for_spawning at ../../src/tbb/scheduler.cpp:570
#4 tbb::internal::generic_scheduler::local_spawn at ../../src/tbb/scheduler.cpp:583
#5 spawn at /usr/include/tbb/task.h:900
#6 execute<tbb::interface6::internal::start_for<tbb::blocked_range<unsigned int>, ApplyPar2CreatorRSProcess, tbb::affinity_partitioner>, tbb::blocked_range<unsigned int> > at /usr/include/tbb/partitioner.h:258
#7 tbb::interface6::internal::start_for<tbb::blocked_range<unsigned int>, ApplyPar2CreatorRSProcess, tbb::affinity_partitioner>::execute at /usr/include/tbb/parallel_for.h:116
#8 tbb::internal::custom_scheduler<tbb::internal::IntelSchedulerTraits>::local_wait_for_all at ../../src/tbb/custom_scheduler.h:448
#9 tbb::internal::generic_scheduler::local_spawn_root_and_wait at ../../src/tbb/scheduler.cpp:630
Created attachment 754889 [details]
Created attachment 754890 [details]
Created attachment 754891 [details]
Created attachment 754892 [details]
Created attachment 754893 [details]
Created attachment 754894 [details]
Created attachment 754895 [details]
Created attachment 754896 [details]
Created attachment 754897 [details]
Created attachment 754898 [details]
@Petr Machata: the backtrace mentioned in this ticket contain a large amount of tbb-specific frames. Does the stacktrace ring any bells to you?
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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 18'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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.