Subject: Discussion related to cado-nfs
List archive
- From: meng <qsmeng@126.com>
- To: "Alexander Kruppa" <alexander.kruppa@inria.fr>
- Cc: paul.zimmermann@loria.fr, "cado-nfs-discuss@lists.gforge.inria.fr" <cado-nfs-discuss@lists.gforge.inria.fr>
- Subject: Re: [Cado-nfs-discuss] problem in sieve stage
- Date: Fri, 19 Jul 2013 21:33:29 +0800 (CST)
- List-archive: <http://lists.gforge.inria.fr/pipermail/cado-nfs-discuss>
- List-id: A discussion list for Cado-NFS <cado-nfs-discuss.lists.gforge.inria.fr>
Dear Alex,
>>in another redhat el5 computer, if i run ./factor.sh >> 90377629292003121684002147101760858109247336549001090677693 -t 4 -v, >> i get " >> Error:Command `env nice -0 >> /home/greatnet/cado-nfs/build/master/sieve/las -I 11 -rpowlim 2047 >> -apowlim 2047 -poly /tmp/cado.QQVgf15501/c59.poly -fb >> /tmp/cado.QQVgf15501/c59.roots -q0 200000 -q1 202000 -mt 4 -out >> /tmp/cado.QQVgf15501/c59.rels.200000-202000.gz > /dev/null 2>&1' >> terminated unexpectedly with exit status 134. >> Error:STDERR sh: line 1: 15707 Aborted env nice -0 >> /home/greatnet/cado-nfs/build/master/sieve/las -I 11 -rpowlim 2047 >> -apowlim 2047 -poly /tmp/cado.QQVgf15501/c59.poly -fb >> /tmp/cado.QQVgf15501/c59.roots -q0 200000 -q1 202000 -mt 4 -out >> /tmp/cado.QQVgf15501/c59.rels.200000-202000.gz > /dev/null 2>&1 >> FAILED ; data left in /tmp/cado.QQVgf15501 >> " >> if i run ./factor.sh >> 90377629292003121684002147101760858109247336549001090677693 -t 4 >> -ssh >> the computer repeat the sieve again an >> d again, but without any rels obtained, also no error reported. > >> Thank you! >> regards, >> meng > > >Exit code 134 looks like an abort, probably from a failed assertion, but due to stdout and stderr redirection, it does not print the error message of the failed assertion. I could not reproduce the error here, so I could not find out which assertion it was. > >What happens if you run the command > >/home/greatnet/cado-nfs/build/master/sieve/las -I 11 -rpowlim 2047 \ > -apowlim 2047 -poly /tmp/cado.QQVgf15501/c59.poly \ > -fb /tmp/cado.QQVgf15501/c59.roots -q0 200000 -q1 202000 -mt 4 \ > -out /tmp/cado.QQVgf15501/c59.rels.200000-202000.gz > >on that machine? If it aborts again, it should print the error message. > >Thanks, >Alex
After running the above command, I got the following message:
*** glibc detected *** /home/greatnet/meng/cado-nfs/build/master/sieve/las: free(): invalid next size (fast): 0x00002ad49c000fe0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x39f5a7166f]
/lib64/libc.so.6(cfree+0x4b)[0x39f5a7589b]
/home/greatnet/meng/cado-nfs/build/master/sieve/las(process_bucket_region+0x1312)[0x40a772]
/lib64/libpthread.so.0[0x39f660683d]
/lib64/libc.so.6(clone+0x6d)[0x39f5ad4fad]
======= Memory map: ========
00400000-0044b000 r-xp 00000000 08:03 8357616 /home/greatnet/meng/cado-nfs/build/master/sieve/las
0064a000-0064b000 rw-p 0004a000 08:03 8357616 /home/greatnet/meng/cado-nfs/build/master/sieve/las
0064b000-0064e000 rw-p 0064b000 00:00 0
01618000-01f48000 rw-p 01618000 00:00 0 [heap]
39f5600000-39f561c000 r-xp 00000000 08:03 47775768 /lib64/ld-2.5.so
39f581c000-39f581d000 r--p 0001c000 08:03 47775768 /lib64/ld-2.5.so
39f581d000-39f581e000 rw-p 0001d000 08:03 47775768 /lib64/ld-2.5.so
39f5a00000-39f5b4f000 r-xp 00000000 08:03 47775770 /lib64/libc-2.5.so
39f5b4f000-39f5d4e000 ---p 0014f000 08:03 47775770 /lib64/libc-2.5.so
39f5d4e000-39f5d52000 r--p 0014e000 08:03 47775770 /lib64/libc-2.5.so
39f5d52000-39f5d53000 rw-p 00152000 08:03 47775770 /lib64/libc-2.5.so
39f5d53000-39f5d58000 rw-p 39f5d53000 00:00 0
39f6200000-39f6282000 r-xp 00000000 08:03 47775829 /lib64/libm-2.5.so
39f6282000-39f6481000 ---p 00082000 08:03 47775829 /lib64/libm-2.5.so
39f6481000-39f6482000 r--p 00081000 08:03 47775829 /lib64/libm-2.5.so
39f6482000-39f6483000 rw-p 00082000 08:03 47775829 /lib64/libm-2.5.so
39f6600000-39f6616000 r-xp 00000000 08:03 47775940 /lib64/libpthread-2.5.so
39f6616000-39f6816000 ---p 00016000 08:03 47775940 /lib64/libpthread-2.5.so
39f6816000-39f6817000 r--p 00016000 08:03 47775940 /lib64/libpthread-2.5.so
39f6817000-39f6818000 rw-p 00017000 08:03 47775940 /lib64/libpthread-2.5.so
39f6818000-39f681c000 rw-p 39f6818000 00:00 0
3a04800000-3a0480d000 r-xp 00000000 08:03 47775930 /lib64/libgcc_s-4.1.2-20080825.so.1
3a0480d000-3a04a0d000 ---p 0000d000 08:03 47775930 /lib64/libgcc_s-4.1.2-20080825.so.1
3a04a0d000-3a04a0e000 rw-p 0000d000 08:03 47775930 /lib64/libgcc_s-4.1.2-20080825.so.1
3a08000000-3a080e6000 r-xp 00000000 08:03 23041780 /usr/lib64/libstdc++.so.6.0.8
3a080e6000-3a082e5000 ---p 000e6000 08:03 23041780 /usr/lib64/libstdc++.so.6.0.8
3a082e5000-3a082eb000 r--p 000e5000 08:03 23041780 /usr/lib64/libstdc++.so.6.0.8
3a082eb000-3a082ee000 rw-p 000eb000 08:03 23041780 /usr/lib64/libstdc++.so.6.0.8
3a082ee000-3a08300000 rw-p 3a082ee000 00:00 0
2ad498670000-2ad498672000 rw-p 2ad498670000 00:00 0
2ad498672000-2ad4986a6000 r-xp 00000000 08:03 8357407 /home/greatnet/meng/cado-nfs/build/master/utils/libutils.so
2ad4986a6000-2ad4988a5000 ---p 00034000 08:03 8357407 /home/greatnet/meng/cado-nfs/build/master/utils/libutils.so
2ad4988a5000-2ad4988a6000 rw-p 00033000 08:03 8357407 /home/greatnet/meng/cado-nfs/build/master/utils/libutils.so
2ad4988a6000-2ad4988a7000 rw-p 2ad4988a6000 00:00 0
2ad4988bc000-2ad4988bd000 rw-p 2ad4988bc000 00:00 0
2ad4988bd000-2ad498928000 r-xp 00000000 08:03 23058384 /usr/local/lib/libgmp.so.10.1.2
2ad498928000-2ad498b28000 ---p 0006b000 08:03 23058384 /usr/local/lib/libgmp.so.10.1.2
2ad498b28000-2ad498b31000 rw-p 0006b000 08:03 23058384 /usr/local/lib/libgmp.so.10.1.2
2ad498b31000-2ad498bb7000 rw-p 2ad498b31000 00:00 0
2ad498c36000-2ad4990c1000 rw-p 2ad498c36000 00:00 0
2ad4990c1000-2ad4990c2000 ---p 2ad4990c1000 00:00 0
2ad4990c2000-2ad499ac2000 rw-p 2ad4990c2000 00:00 0
2ad49a13e000-2ad49a13f000 ---p 2ad49a13e000 00:00 0
2ad49a13f000-2ad49ab3f000 rw-p 2ad49a13f000 00:00 0
2ad49ab3f000-2ad49ab40000 ---p 2ad49ab3f000 00:00 0
2ad49ab40000-2ad49b540000 rw-p 2ad49ab40000 00:00 0
2ad49b540000-2ad49b541000 ---p 2ad49b540000 00:00 0
2ad49b541000-2ad49bf41000 rw-p 2ad49b541000 00:00 0
2ad49c000000-2ad49c234000 rw-p 2ad49c000000 00:00 0
2ad49c234000-2ad4a0000000 ---p 2ad49c234000 00:00 0
2ad4a0000000-2ad4a0267000 rw-p 2ad4a0000000 00:00 0
2ad4a0267000-2ad4a4000000 ---p 2ad4a0267000 00:00 0
7fff93767000-7fff9377c000 rw-p 7ffffffe9000 00:00 0 [stack]
7fff937fd000-7fff93800000 r-xp 7fff937fd000 00:00 0 [vdso]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0 [vsyscall]
Aborted
Thank you. And happy weekend.
Regards,
Meng
- [Cado-nfs-discuss] problem in sieve stage, meng, 07/08/2013
- Re: [Cado-nfs-discuss] problem in sieve stage, Alexander Kruppa, 07/08/2013
- <Possible follow-up(s)>
- Re: [Cado-nfs-discuss] problem in sieve stage, meng, 07/19/2013
- Re: [Cado-nfs-discuss] problem in sieve stage, Emmanuel Thomé, 07/19/2013
- Re: [Cado-nfs-discuss] problem in sieve stage, Zimmermann Paul, 07/22/2013
- Re: [Cado-nfs-discuss] problem in sieve stage, Emmanuel Thomé, 07/19/2013
Archive powered by MHonArc 2.6.19+.