CADO NFS - Page 8

bai · 2012-06-06, 01:39

BWetter246, I can't re-trigger the error.

Here is the configuration (output by make),

Code:

Configuring gf2x with options --disable-shared --disable-dependency-tracking CFLAGS=-std=c99 -g -W -Wall -O2 -I/usr/include CXXFLAGS=-g -W -Wall -O2 -I/usr/include
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... none
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 3458764513820540925
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... no
checking whether to build static libraries... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) none
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking warning verbosity option... for C++ -Wall -W for C
checking for gcc option to accept ISO C99... none needed
checking build system compiler gcc... yes
checking for build system executable suffix...
checking whether gcc and cc understand -c and -o together... yes
checking size of unsigned long... 8
checking whether gcc can compile sse-2 code... yes
checking whether gcc can compile pclmulqdq and if it is supported by the hardware... no
checking the number of bits in an unsigned long... 64
configure: using ABI="default"
configure: CC="gcc"
configure: CFLAGS="-Wall -W -std=c99 -g -W -Wall -O2 -I/usr/include"
configure: CPPFLAGS=""
configure: hwdir="x86_64"
checking whether already_tuned/x86_64/ is right assuming 64-bits unsigned longs... yes
configure: creating ./config.status

and gcc -v

Code:

gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

Are there any obvious differences to yours?

BWetter246 · 2012-06-11, 06:07

I managed to compile the software package, but it seems to hang when I try to use the example in the readme. './factor.sh 90377629292003121684002147101760858109247336549001090677693'

Code:

Info:--------------------------------------------------------------------------
Info:Initialization
Info:--------------------------------------------------------------------------
Info:Reading the parameters...
Info:Initializing the working directory...
Info:--------------------------------------------------------------------------
Info:Polynomial selection
Info:--------------------------------------------------------------------------
Info:Total interval coverage:   0 %.
Info:Starting job: 0        5000

BWetter246 · 2012-06-11, 06:09

gcc version

Code:

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/i686-linux-gnu/4.6/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

jasonp · 2012-06-11, 11:46

CADO-NFS has several mailing lists; the developers all read them, so you would get help more quickly if you used them. link. The project pages also have a bug tracker you can use

bai · 2012-06-13, 00:21

Quote:

Originally Posted by BWetter246

I managed to compile the software package, but it seems to hang when I try to use the example in the readme. './factor.sh 90377629292003121684002147101760858109247336549001090677693'

Could you please try revision on/after 0753f50 in git?

Btw: just curious - what's the cpu? (considering "i686-pc-linux-gnu" & size of unsigned long... 4)

BWetter246 · 2012-06-13, 03:47

the processor is an Intel P4. The reason why the script is hanging is because I believe the number is too small. When I try the RSA100 number, polyselect2l crashes.

Code:

Info:--------------------------------------------------------------------------
Info:Initialization
Info:--------------------------------------------------------------------------
Info:Reading the parameters...
Info:Initializing the working directory...
Info:--------------------------------------------------------------------------
Info:Polynomial selection
Info:--------------------------------------------------------------------------
Info:Total interval coverage:   0 %.
Info:Starting job: 0        10000   
    Error:Command `env nice -0 /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l -q -lq 3 -nq 1000 -incr 210 -admin 0 -admax 10000 -degree 4 -maxnorm 35.0 -t 1 50000 < /tmp/cado.X2RbEedTH0/c100.n > /tmp/cado.X2RbEedTH0/c100.polsel_out.0-10000 2>&1' terminated unexpectedly with exit status 134.
FAILED ; data left in /tmp/cado.X2RbEedTH0

c100.polsel.out

Code:

# /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l -q -lq 3 -nq 1000 -incr 210 -admin 0 -admax 10000 -degree 4 -maxnorm 35.0 -t 1 50000
*** glibc detected *** /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l: free(): invalid pointer: 0xb6e090a0 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x73e42)[0x233e42]
/usr/lib/i386-linux-gnu/libgmp.so.10(__gmp_default_free+0x1b)[0x894d9b]
/usr/lib/i386-linux-gnu/libgmp.so.10(__gmpz_clear+0x2a)[0x89f70a]
/home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l(comp_sq_roots+0x1ae)[0x805002e]
/home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l[0x804d2ff]
/home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l(one_thread+0x40a)[0x804daba]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0x631d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x2aaace]
======= Memory map: ========
00110000-0012c000 r-xp 00000000 08:01 916660     /lib/i386-linux-gnu/libgcc_s.so.1
0012c000-0012d000 r--p 0001b000 08:01 916660     /lib/i386-linux-gnu/libgcc_s.so.1
0012d000-0012e000 rw-p 0001c000 08:01 916660     /lib/i386-linux-gnu/libgcc_s.so.1
001bf000-001c0000 r-xp 00000000 00:00 0          [vdso]
001c0000-0035f000 r-xp 00000000 08:01 916639     /lib/i386-linux-gnu/libc-2.15.so
0035f000-00361000 r--p 0019f000 08:01 916639     /lib/i386-linux-gnu/libc-2.15.so
00361000-00362000 rw-p 001a1000 08:01 916639     /lib/i386-linux-gnu/libc-2.15.so
00362000-00365000 rw-p 00000000 00:00 0 
0062b000-00642000 r-xp 00000000 08:01 916719     /lib/i386-linux-gnu/libpthread-2.15.so
00642000-00643000 r--p 00016000 08:01 916719     /lib/i386-linux-gnu/libpthread-2.15.so
00643000-00644000 rw-p 00017000 08:01 916719     /lib/i386-linux-gnu/libpthread-2.15.so
00644000-00646000 rw-p 00000000 00:00 0 
0082f000-00859000 r-xp 00000000 08:01 916671     /lib/i386-linux-gnu/libm-2.15.so
00859000-0085a000 r--p 00029000 08:01 916671     /lib/i386-linux-gnu/libm-2.15.so
0085a000-0085b000 rw-p 0002a000 08:01 916671     /lib/i386-linux-gnu/libm-2.15.so
0088c000-00903000 r-xp 00000000 08:01 2097835    /usr/lib/i386-linux-gnu/libgmp.so.10.0.2
00903000-00904000 r--p 00076000 08:01 2097835    /usr/lib/i386-linux-gnu/libgmp.so.10.0.2
00904000-0090b000 rw-p 00077000 08:01 2097835    /usr/lib/i386-linux-gnu/libgmp.so.10.0.2
00934000-00942000 r-xp 00000000 08:01 1837184    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/libpolyselect_common.so
00942000-00943000 r--p 0000d000 08:01 1837184    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/libpolyselect_common.so
00943000-00944000 rw-p 0000e000 08:01 1837184    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/libpolyselect_common.so
00d96000-00db6000 r-xp 00000000 08:01 916619     /lib/i386-linux-gnu/ld-2.15.so
00db6000-00db7000 r--p 0001f000 08:01 916619     /lib/i386-linux-gnu/ld-2.15.so
00db7000-00db8000 rw-p 00020000 08:01 916619     /lib/i386-linux-gnu/ld-2.15.so
00ecf000-00efb000 r-xp 00000000 08:01 1837119    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/utils/libutils.so
00efb000-00efc000 r--p 0002b000 08:01 1837119    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/utils/libutils.so
00efc000-00efd000 rw-p 0002c000 08:01 1837119    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/utils/libutils.so
08048000-08064000 r-xp 00000000 08:01 1837232    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l
08064000-08065000 r--p 0001c000 08:01 1837232    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l
08065000-08066000 rw-p 0001d000 08:01 1837232    /home/bwetter246/Documents/cado-nfs/build/bwetter246-Linux/polyselect/polyselect2l
084ca000-084eb000 rw-p 00000000 00:00 0          [heap]
b6e00000-b6e28000 rw-p 00000000 00:00 0 
b6e28000-b6f00000 ---p 00000000 00:00 0 
b6f1b000-b6f1c000 ---p 00000000 00:00 0 
b6f1c000-b771e000 rw-p 00000000 00:00 0 
b772b000-b7731000 rw-p 00000000 00:00 0 
bfdd5000-bfdf6000 rw-p 00000000 00:00 0          [stack]
# Info: initializing 4459 P primes took 0ms, seed=1339558903, rawonly=0, nq=1000, target_time=10000
# Info: estimated peak memory=0.00MB (1 thread(s), batch 10 inversions on SQ)
Aborted (core dumped)

bai · 2012-06-18, 07:03

Quote:

Originally Posted by BWetter246

the processor is an Intel P4. The reason why the script is hanging is because I believe the number is too small. When I try the RSA100 number, polyselect2l crashes.

I think it is not the number size, but the 32bit portability of polyselect/*. I've updated some codes just now (git rev. dcabf90). They're working on a gentoo-3.3.0-atom 32-bit x86. Hopefully it also works on a P4.

BWetter246 · 2012-06-18, 17:59

thanks bai, the new repository revision works.

skan · 2012-12-08, 14:05

Hello

Did anybody get to compile it for Windows?

Dubslow · 2016-03-16, 05:45

Seems that CADO has switched from Perl to Python without anyone here noticing.

xilman · 2016-03-16, 07:24

Quote:

Originally Posted by Dubslow

Seems that CADO has switched from Perl to Python without anyone here noticing.

I noticed long since. In fact I had a discussion with the dev team about the switch.

Silence may be golden but it's not necessarily an indication of ignorance.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CADO-NFS on windows	jux	CADO-NFS	25	2021-07-13 23:53
CADO help	henryzz	CADO-NFS	4	2017-11-20 15:14
CADO and WinBlows	akruppa	Programming	22	2015-12-31 08:37
CADO-NFS	skan	Information & Answers	1	2013-10-22 07:00
CADO	R.D. Silverman	Factoring	4	2008-11-06 12:35

2012-06-11, 11:46	#81
jasonp Tribal Bullet Oct 2004 3,541 Posts	CADO-NFS has several mailing lists; the developers all read them, so you would get help more quickly if you used them. link. The project pages also have a bug tracker you can use

2012-06-18, 17:59	#85
BWetter246 Aug 2005 17 Posts	thanks bai, the new repository revision works.

2012-12-08, 14:05	#86
skan Apr 2012 2·47 Posts	Hello Did anybody get to compile it for Windows?

2016-03-16, 05:45	#87
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 1C35₁₆ Posts	Seems that CADO has switched from Perl to Python without anyone here noticing.