Red Hat Bugzilla – Bug 592906
[abrt] crash in hardinfo-0.5.1-2.fc12: lup_solve: Process /usr/bin/hardinfo was killed by signal 11 (SIGSEGV)
Last modified: 2011-06-27 12:25:36 EDT
abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: hardinfo comment: while making a benchmark, hardinfo crashes.. component: hardinfo crash_function: lup_solve executable: /usr/bin/hardinfo global_uuid: 061014484bd5f6411bc328534ef1ad3ff92b35e6 kernel: 2.6.32.11-99.fc12.i686.PAE package: hardinfo-0.5.1-2.fc12 rating: 4 reason: Process /usr/bin/hardinfo was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 414515 [details] File: backtrace
Package: hardinfo-0.5.1-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) Comment ----- while making a benchmark, hardinfo crashes.. by FFT...
Package: hardinfo-0.5.1-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- hardinfo is crashing by testing FFT
Package: hardinfo-0.5.1-2.fc12 Architecture: i686 OS Release: Fedora release 13 (Goddard) Comment ----- Hardinfo crashes by Benchmarks > FPU FFT
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13'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 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.