Software/instructions/questions

[Puzzle-Peter]

Following Mark's instructions, I tried the failing primality test from the command line, using pfgw32 and pfgw64 version 3.4.5 for Linux. They both worked. So I tried running the running the script again. pgw32 worked, pfgw64 produced the SIGILL error as described.

So here's the script I was using, there seems to be no way to attach it to a personal message to Mark. This post can be deleted as soon as he gets the attachment.

Thanks,
Peter

[rogue]

Originally Posted by Puzzle-Peter

Following Mark's instructions, I tried the failing primality test from the command line, using pfgw32 and pfgw64 version 3.4.5 for Linux. They both worked. So I tried running the running the script again. pgw32 worked, pfgw64 produced the SIGILL error as described.

So here's the script I was using, there seems to be no way to attach it to a personal message to Mark. This post can be deleted as soon as he gets the attachment.

Thanks,
Peter

I presume you used -f30 with this script. It works on Win64, so I'll need to get access to a Linux box in order to debug it.

BTW, if I can't reproduce on a Linux box available to me, would you be able to get me access to your box so that I can debug on it?

[Puzzle-Peter]

Originally Posted by rogue

I presume you used -f30 with this script. It works on Win64, so I'll need to get access to a Linux box in order to debug it.

BTW, if I can't reproduce on a Linux box available to me, would you be able to get me access to your box so that I can debug on it?

Ugh, yes I forgot to mention -f30.

These boxes aren't even online, I transfer data via USB stick. I haven't got admin permissions either. Sorry! But I'll be happy to carry out any instructions you give me. It will be a slow and awkward process though.

[rogue]

Originally Posted by Puzzle-Peter

Ugh, yes I forgot to mention -f30.

These boxes aren't even online, I transfer data via USB stick. I haven't got admin permissions either. Sorry! But I'll be happy to carry out any instructions you give me. It will be a slow and awkward process though.

It would be rather hard to do this on an off-line box. You need the sources and a compiler (gcc) and the debugging tool (gdb). If you can do these things, then talk to me off-line via my e-mail address.

[rogue]

Steven Harvey has been able to reproduce the problem on his Linux box (where PFGW is built from). He has given me ssh access so I am going to debug it there.

[Puzzle-Peter]

Originally Posted by rogue

Steven Harvey has been able to reproduce the problem on his Linux box (where PFGW is built from). He has given me ssh access so I am going to debug it there.

That's great! gcc is available to me, but not gdb...

BTW: is there a way to completely suppress screen output? The program ploughs through the k's so fast I am afraid output may slow down the whole thing. I know it does for the sieves at low p levels when run without -q.

[rogue]

Originally Posted by Puzzle-Peter

That's great! gcc is available to me, but not gdb...

BTW: is there a way to completely suppress screen output? The program ploughs through the k's so fast I am afraid output may slow down the whole thing. I know it does for the sieves at low p levels when run without -q.

d/l 3.4.6 and use -Cquiet.

[Puzzle-Peter]

Originally Posted by rogue

d/l 3.4.6 and use -Cquiet.

Thanks!

[rogue]

Originally Posted by Puzzle-Peter

Following Mark's instructions, I tried the failing primality test from the command line, using pfgw32 and pfgw64 version 3.4.5 for Linux. They both worked. So I tried running the running the script again. pgw32 worked, pfgw64 produced the SIGILL error as described.

So here's the script I was using, there seems to be no way to attach it to a personal message to Mark. This post can be deleted as soon as he gets the attachment.

Thanks,
Peter

I have fixed the problem, or at least I think I have. I rebuilt GMP using "generic x86" instructions and this no longer fails. I hope to re-release the Linux soon.

[Puzzle-Peter]

I started sieving for S63 using srsieve. I specified -f but for some reason did not get factor files, so now I have different srsieve.out files each with a number of candidates removed.

I can extract the removed candidates for each output file and then remove them all from the original sieve file using an awk script several times (once for each core), but it's a bit awkward. Can srfile or some other tool be used for this?

Thanks
Peter

[rogue]

Originally Posted by Puzzle-Peter

I started sieving for S63 using srsieve. I specified -f but for some reason did not get factor files, so now I have different srsieve.out files each with a number of candidates removed.

I can extract the removed candidates for each output file and then remove them all from the original sieve file using an awk script several times (once for each core), but it's a bit awkward. Can srfile or some other tool be used for this?

Thanks
Peter

srsieve will remove the factors automatically. You don't need to worry about saving off factors. Use srsieve -a to create the .abcd file needed for sr2sieve. That will create a factor file that srfile can use to remove factors. When using sr2sieve, you probably want to specify the -x option so that it doesn't generate Legendre symbols.