View Single Post
Old 2021-09-01, 14:22   #8
Dec 2020

71 Posts

Originally Posted by kruoli View Post
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?
~/Math/ggnfs/src/experimental/lasieve4_64$ gdb --args gnfs-lasieve4I14e -r ../../../bin/testing/best -o out -f 40000000 -c 2000
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
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_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnfs-lasieve4I14e...
(gdb) run
Starting program: /home/uwu/Math/ggnfs/src/experimental/lasieve4_64/gnfs-lasieve4I14e -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 gnfs-lasieve4e.c:2085
I should have probably mentioned this earlier, but I'm using EdH's patches for GGNFS from
Plutie is offline   Reply With Quote