Trouble updating to most recent wip (and sigma question)

EdH · 2020-09-30, 13:38

I started out with the below question about sigma(), but I decided to make sure I had the latest and greatest ("Updated to revision 390.") and now I get:

Code:

$ ./yafu
Segmentation fault (core dumped)

or:

Code:

$ ./yafu "sigma(951452727946218710,1)-951452727946218710"
Segmentation fault (core dumped)

Header from previous (working) YAFU version:

Code:

09/30/20 08:21:01 v1.35-beta @ math99, System/Build Info: 
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.0
detected       Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
detected L1 = 32768 bytes, L2 = 15728640 bytes, CL = 64 bytes

I tried earlier revisions and 388 and below work, while 389 and 390 crash.

===================================
Original question while YAFU was working:

Is there a way to get just the result from a command line invocation of sigma()?

-silent appears to only suppress empty lines.

With -silent

Code:

$ ./yafu "sigma(951452727946218710,1)-951452727946218710" -silent
applying option threads=24
applying option aprcl_p=500
applying option aprcl_d=200
applying option ggnfs_dir=/home/math99/Math/ggnfs/bin/
applying option B1ecm=11000
applying option ecm_path=/usr/local/bin/ecm
applying option B1pm1=20000
applying option tune_info=      Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz,LINUX64,3.79646e-05,0.193141,0.547899,0.0979439,100.603,2094.92
769573579531517290

Without -silent:

Code:

$ ./yafu "sigma(951452727946218710,1)-951452727946218710"
applying option threads=24
applying option aprcl_p=500
applying option aprcl_d=200
applying option ggnfs_dir=/home/math99/Math/ggnfs/bin/
applying option B1ecm=11000
applying option ecm_path=/usr/local/bin/ecm
applying option B1pm1=20000
applying option tune_info=      Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz,LINUX64,3.79646e-05,0.193141,0.547899,0.0979439,100.603,2094.92


769573579531517290

The result isn't returned in either factor.log (not really expected), or session log (expected):

factor.log:

Code:

09/30/20 08:27:48 v1.35-beta @ math99, 
09/30/20 08:27:48 v1.35-beta @ math99, ****************************
09/30/20 08:27:48 v1.35-beta @ math99, Starting factorization of 951452727946218710
09/30/20 08:27:48 v1.35-beta @ math99, using pretesting plan: normal
09/30/20 08:27:48 v1.35-beta @ math99, using tune info for qs/gnfs crossover
09/30/20 08:27:48 v1.35-beta @ math99, ****************************
09/30/20 08:27:48 v1.35-beta @ math99, div: found prime factor = 2
09/30/20 08:27:48 v1.35-beta @ math99, div: found prime factor = 5
09/30/20 08:27:48 v1.35-beta @ math99, div: found prime factor = 349
09/30/20 08:27:48 v1.35-beta @ math99, div: found prime factor = 491
09/30/20 08:27:48 v1.35-beta @ math99, Fermat method found factors:
09/30/20 08:27:48 v1.35-beta @ math99, prp7 = 1660261
09/30/20 08:27:48 v1.35-beta @ math99, prp6 = 334429
09/30/20 08:27:48 v1.35-beta @ math99, Total factoring time = 0.0072 seconds

session.log appears to just tease:

Code:

09/30/20 08:27:48 v1.35-beta @ math99, System/Build Info: 
09/30/20 08:27:48 v1.35-beta @ math99, cached 664579 primes. pmax = 9999991
09/30/20 08:27:48 v1.35-beta @ math99, detected       Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
detected L1 = 32768 bytes, L2 = 15728640 bytes, CL = 64 bytes
09/30/20 08:27:48 v1.35-beta @ math99, measured cpu frequency ~= 2094.922920
09/30/20 08:27:48 v1.35-beta @ math99, using 1 random witnesses for Rabin-Miller PRP checks

09/30/20 08:27:48 v1.35-beta @ math99, New random seeds: 2719837668, 2882061925

09/30/20 08:27:48 v1.35-beta @ math99, Processing: sigma(951452727946218710,1)-951452727946218710
09/30/20 08:27:48 v1.35-beta @ math99, Result    :

Thanks for any help!

bsquared · 2020-09-30, 14:49

As usual, thanks for your diligent usage and testing. You can try r392 now.

I've tested a few of the basics with
1) NFS=1 USE_AVX2=1 USE_BMI2=1 SKYLAKEX=1
2) NFS=1 USE_AVX2=1
3) NFS=1 USE_SSE41=1

with both gcc 7.3.0 and icc on linux. No crashes so far.

Sigma (indeed, any command), will now return a result into session.log. The .ini initialization is now quieter by default as well.

EdH · 2020-09-30, 15:18

Quote:

Originally Posted by bsquared

As usual, thanks for your diligent usage and testing. You can try r392 now.

I've tested a few of the basics with
1) NFS=1 USE_AVX2=1 USE_BMI2=1 SKYLAKEX=1
2) NFS=1 USE_AVX2=1
3) NFS=1 USE_SSE41=1

with both gcc 7.3.0 and icc on linux. No crashes so far.

Sigma (indeed, any command), will now return a result into session.log. The .ini initialization is now quieter by default as well.

Thanks much! It is now returning the result in session.log, but I'm only getting r391 and still seeing all the initialization.

bsquared · 2020-09-30, 15:21

Quote:

Originally Posted by EdH

Thanks much! It is now returning the result in session.log, but I'm only getting r391 and still seeing all the initialization.

Oops, forgot to commit that - should be there now.

EdH · 2020-09-30, 15:31

Quote:

Originally Posted by bsquared

Oops, forgot to commit that - should be there now.

Excellent! Thanks much!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
what does sigma mean in ECM?	bbb120	GMP-ECM	7	2021-01-26 16:18
sigma(n)=x*(x+1)^3	enzocreti	enzocreti	3	2020-09-29 12:12
Sigma parameter in ecm	storm5510	Information & Answers	4	2019-11-30 21:32
PRP vs. LL (was: Changes to Recent Cleared and Recent Results)	petrw1	PrimeNet	32	2019-04-09 10:44
Iteration of (sigma(n)+phi(n))/2	sean	Factoring	2	2017-09-18 15:39

2020-09-30, 14:49	#2
bsquared "Ben" Feb 2007 3,371 Posts	As usual, thanks for your diligent usage and testing. You can try r392 now. I've tested a few of the basics with 1) NFS=1 USE_AVX2=1 USE_BMI2=1 SKYLAKEX=1 2) NFS=1 USE_AVX2=1 3) NFS=1 USE_SSE41=1 with both gcc 7.3.0 and icc on linux. No crashes so far. Sigma (indeed, any command), will now return a result into session.log. The .ini initialization is now quieter by default as well.