Setting SAGE_CHECK=yes just means that after building the pari library, the self-test routines are also run. It does not affect Sage after the new spkg is installed.
John On Tue, Oct 19, 2010 at 1:32 PM, Jan Groenewald <j...@aims.ac.za> wrote: > Hi > > On Sun, Oct 17, 2010 at 07:16:58PM +0200, Jeroen Demeyer wrote: >> env SAGE_CHECK=yes ./sage -f >> http://sage.math.washington.edu/home/release/sage-4.6.alpha3/sage-4.6.alpha3/spkg/standard/pari-2.4.3.svn-12577.p7.spkg > > This still caused a segfault for me in dmesg while doctests pass. > Is SAGE_CHECK supposed to give more output? Where? > Can I have pari give more output? I'm just guessing wildly here: > > r...@capepoint:~#cd /usr/local/src/sage-4.5.3/spkg/standard/ > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard#tar xjf > pari-2.3.5.p4.spkg > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard#cd pari-2.3.5.p4/ > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard/pari-2.3.5.p4#grep -ri > "DEBUGLEVEL = " * > src/src/language/init.c: DEBUGFILES = DEBUGLEVEL = DEBUGMEM = 0; > src/src/language/init.c: if (oldval >= 0) { DEBUGLEVEL = oldval; oldval = > -1; } > src/src/language/init.c: { oldval = DEBUGLEVEL; DEBUGLEVEL = val; } > src/src/functions/programming/default: ("debug",small):small:parens > DEBUGLEVEL = $2 > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard/pari-2.3.5.p4#sed -i > 's/DEBUGFILES = DEBUGLEVEL = DEBUGMEM = 0;/DEBUGFILES = DEBUGLEVEL = DEBUGMEM > = 9;/' src/src/language/init.c > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard/pari-2.3.5.p4#cd ../ > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard#sage -spkg > pari-2.3.5.p4 > Creating Sage package pari-2.3.5.p4 > ... > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard#env SAGE_CHECK=yes > sage -f pari-2.3.5.p4.spkg > Force installing pari-2.3.5.p4.spkg > ... > Finished installing pari-2.3.5.p4.spkg > r...@capepoint:/usr/local/src/sage-4.5.3/spkg/standard#dmesg|grep segfault|wc > -l; sage -t devel/sage/sage/interfaces/sage0.py; dmesg|grep segfault > 0 > sage -t "devel/sage/sage/interfaces/sage0.py" > [18.2 s] > > ---------------------------------------------------------------------- > All tests passed! > Total time for all tests: 18.2 seconds > [79234.381854] python[17992]: segfault at 72000000ae ip 00007f3fce620fa1 sp > 00007fff0a28cbe0 error 4 in libpari-gmp.so.2[7f3fce42c000+2c6000] > > Even if it is slow, is there a way to tell pari to write some output > somewhere? > > regards, > Jan > -- > .~. > /V\ Jan Groenewald > /( )\ www.aims.ac.za > ^^-^^ > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
