20210901, 04:02  #1 
"Evan"
Dec 2020
Montreal
2^{3}×3^{2} Posts 
Confused w/ GGNFS testsieving
I'm trying to get used to using GGNFS for small testsieving runs, but it keeps quitting with a segfault every time I run it. I'm using the latest svn commit, logs are below:
error: Code:
../gnfslasieve4I14e r best f 40000000 c 2000 o out v gnfslasieve4I14e (with asm64): L1_BITS=15, SVN $Revision: 430 $ Warning: lowering FB_bound to 39999999. FBsize 0+0 (deg 5), 2433653+0 (deg 1) Segmentation fault (core dumped) Code:
n: 34166954268223117586694342692657229016949491449884020389380916912810751648547993862665918137895802414087143647172456606010982099550483495609252531569046466515647 Y0: 13603872162482730571699689045336 Y1: 17861405487832127 c0: 697905031491851072220557657635373187641 c1: 540258594997580854184116508876581 c2: 321067102369857480091237224 c3: 24849778917509463073 c4: 3323710111783 c5: 73332 skew: 7208184.563 # lognorm 50.36, E 43.24, alpha 7.13 (proj 1.21), 5 real roots # MurphyE(Bf=1.000e+07,Bg=5.000e+06,area=1.000e+16)=1.265e12 rlim: 67000000 alim: 67000000 lpbr: 30 lpba: 30 mfbr: 60 mfba: 60 rlambda: 2.6 alambda: 2.6 type: gnfs lss: 0 Any help would really be appreciated, thank you! 
20210901, 04:46  #2 
"Curtis"
Feb 2005
Riverside, CA
5^{2}×7×29 Posts 
Do you have evidence that your compiled GGNFS binaries work? That is, do they function when called by factmsieve.py or yafu?
If not, acquire working binaries or run one of those scripts to determine if your binaries work. I've never successfully compiled GGNFS, but I haven't tried very hard; there have been almost no changes to the code in ten years. 
20210901, 05:25  #3  
"Evan"
Dec 2020
Montreal
72_{10} Posts 
Quote:
Code:
elapsed time: 20.1866 seconds (101 second deadline); poly select done nfs: commencing algebraic side lattice sieving over range: 900000  901667 nfs: commencing algebraic side lattice sieving over range: 918337  920004 nfs: commencing algebraic side lattice sieving over range: 901667  903334 nfs: commencing algebraic side lattice sieving over range: 905001  906668 nfs: commencing algebraic side lattice sieving over range: 908335  910002 nfs: commencing algebraic side lattice sieving over range: 903334  905001 nfs: commencing algebraic side lattice sieving over range: 906668  908335 nfs: commencing algebraic side lattice sieving over range: 910002  911669 nfs: commencing algebraic side lattice sieving over range: 911669  913336 nfs: commencing algebraic side lattice sieving over range: 913336  915003 nfs: commencing algebraic side lattice sieving over range: 915003  916670 nfs: commencing algebraic side lattice sieving over range: 916670  918337 total yield: 20462, q=903337 (0.00065 sec/rel) total yield: 23162, q=915007 (0.00063 sec/rel) total yield: 23559, q=905011 (0.00065 sec/rel) total yield: 24649, q=913337 (0.00065 sec/rel) total yield: 25268, q=906673 (0.00065 sec/rel) total yield: 26434, q=918341 (0.00063 sec/rel) total yield: 26316, q=920011 (0.00064 sec/rel) total yield: 26222, q=911671 (0.00065 sec/rel) total yield: 27597, q=901679 (0.00062 sec/rel) total yield: 27775, q=910003 (0.00064 sec/rel) total yield: 29296, q=908353 (0.00062 sec/rel) total yield: 30366, q=916679 (0.00062 sec/rel) 

20210901, 06:23  #4 
May 2009
Russia, Moscow
2^{7}·3·7 Posts 
You're sieving on rational side while the posted poly is for algebraic side. Did you try a instead of r option?

20210901, 09:28  #5  
Just call me Henry
"David"
Sep 2007
Cambridge (GMT/BST)
2^{2}×3^{3}×5×11 Posts 
Quote:
Two ideas: Can the ggnfs siever understand lss? At best it will ignore it I think. We have had issues in the past with compilers making it so that the r or a option must be the last option. 

20210901, 12:27  #6 
"Evan"
Dec 2020
Montreal
2^{3}×3^{2} Posts 
Tried both of these, no success.

20210901, 13:58  #7 
"Oliver"
Sep 2017
Porta Westfalica, DE
2^{8}·3 Posts 
So both ideas produced an identical segmentation fault?
Edit: Can you build it with g and run it in GDB? Do you have experience with that? Last fiddled with by kruoli on 20210901 at 13:59 Reason: Additions. And missing word added. 
20210901, 14:22  #8  
"Evan"
Dec 2020
Montreal
2^{3}×3^{2} Posts 
Quote:
Code:
~/Math/ggnfs/src/experimental/lasieve4_64$ gdb args gnfslasieve4I14e r ../../../bin/testing/best o out f 40000000 c 2000 GNU gdb (Ubuntu 9.20ubuntu1~20.04) 9.2 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64linuxgnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from gnfslasieve4I14e... (gdb) run Starting program: /home/uwu/Math/ggnfs/src/experimental/lasieve4_64/gnfslasieve4I14e r ../../../bin/testing/best o out f 40000000 c 2000 Program received signal SIGSEGV, Segmentation fault. 0x0000000000427e30 in slinie_fbi_loop () (gdb) bt #0 0x0000000000427e30 in slinie_fbi_loop () #1 0x00000000005d5760 in smallsieve_aux2 () #2 0x0000000000000005 in ?? () #3 0x0000000000406c76 in main (argc=<optimized out>, argv=<optimized out>) at gnfslasieve4e.c:2085 

20210901, 14:38  #9  
"Ed Hall"
Dec 2009
Adirondack Mtns
1016_{16} Posts 
Quote:
I can't take credit as the source of the patches. I got them from someone else on the forum, but I can't remember who that may have been. * I've just been using bsquared binaries that are available in the attachments to that first post. 

20210901, 14:58  #10 
"Evan"
Dec 2020
Montreal
2^{3}·3^{2} Posts 
Changed binaries, it's working perfectly now. Thank you!

20210901, 15:51  #11  
"Ed Hall"
Dec 2009
Adirondack Mtns
1016_{16} Posts 
Quote:
Code:
$ ../gnfslasieve4I14e r testPoly f 40000000 c 2000 o testRels v gnfslasieve4I14e (with asm64): L1_BITS=15, SVN $Revision$ Warning: lowering FB_bound to 39999999. FBsize 3951781+0 (deg 5), 2433653+0 (deg 1) total yield: 2205, q=40002023 (0.22094 sec/rel) 118 Special q, 289 reduction iterations reports: 5785443>2476959>2088570>890333>373860>275017 Number of relations with k rational and l algebraic primes for (k,l)=: Total yield: 2205 0/0 mpqs failures, 1633/711 vain mpqs milliseconds total: Sieve 163389 Sched 0 medsched 71955 TD 28275 (Init 732, MPQS 1298) SieveChange 223578 TD side 0: init/small/medium/large/search: 3026 2316 1769 5295 1933 sieve: init/small/medium/large/search: 2257 34308 1797 48850 2489 TD side 1: init/small/medium/large/search: 3363 891 1734 4778 809 sieve: init/small/medium/large/search: 1523 20163 1794 49621 586 Thanks and glad you're working properly. 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Poly select and testsieving for RSA232  VBCurtis  Operation Kibibit  25  20200107 01:57 
CADONFS and GGNFS sieving  ray10may  Msieve  1  20170414 14:19 
Test Sieving Questions  nstaab1  Lounge  15  20130306 13:48 
ggnfs sieving yield wierdness  jrk  Factoring  10  20090507 17:41 
Resume sieving in GGNFS  nuggetprime  Factoring  5  20070604 14:42 