On Sun, Oct 17, 2010 at 07:16:58PM +0200, Jeroen Demeyer wrote: > 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?
Would it help to try again with a PARI compiled with less aggressive optimizations than our default -O3? For example, env SAGE_DEBUG=yes ./sage -f pari-2.3.5.p4.spkg dmesg | grep segfault | wc -l ./sage -t devel/sage/sage/interfaces/sage0.py dmesg | grep segfault -- 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
