Red Hat Bugzilla – Bug 130594
Program mprime in GIMPS project does not run
Last modified: 2015-01-04 17:09:04 EST
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
GIMPS is the Great Internet Prime Search, a distributed computing
program widely used to search for prime numbers.
The main program, mprime, works with 2.6.7-1.494.2.2 and with prior
kernels but does not work with 2.6.8-1.521. The program aborts with
a shell signal 11.
I tried this on two machines, so I am pretty sure there is a problem.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.run mprime in terminal mode
Actual Results: Program aborts with signal 11.
Expected Results: Should have entered into prime number computation.
can you attach a strace of this app?
Is it available for download somewhere ?
I will be attaching strace output in the next few minutes.
Created attachment 102979 [details]
strace output of mprime (from mprime235.tar.gz) segfaulting on kernel 521
Created attachment 102980 [details]
strace output of mprime (from sprime235.tar.gz) segfaulting on kernel 521
Thank you for showing me the strace. I am a newbie.
Please tell me if the mprime problem I reported is due to mprime, due
to the 2.6.8-1.521 kernel or somewhere else.
Thank you for your help. The GIMPS project and mprime are widely
New features in Version 23.9 of mprime
1) Fixed mprime crash bug that arose when Fedora users upgraded to
(quoting from whatsnew.txt in mprime239.tar.gz)
There's a new release of mprime on the mersenne.org web site. I
haven't tried it yet, but the release notes indicate that it should
fix the crash.
Fedora Core 2 has now reached end of life, and no further updates will be
provided by Red Hat. The Fedora legacy project will be producing further kernel
updates for security problems only.
If this bug has not been fixed in the latest Fedora Core 2 update kernel, please
try to reproduce it under Fedora Core 3, and reopen if necessary, changing the
product version accordingly.
For the sake of completing the historical record:
The bug was in a third-party program (mprime) which is not shipped in RHEL or
Fedora Core and which has since been corrected (as I mentioned in comment #6; I
have since tested that fix and confirmed that the fix is effective).