On 5 April 2011 05:27, William Stein <wst...@gmail.com> wrote: > On Mon, Apr 4, 2011 at 5:01 AM, Bill Hart <goodwillh...@googlemail.com> wrote: >> Is the problem reproducible? >> >> If so, a valgrind log would be useful to debug the problem. It should >> find the source of any segfault. zn_poly would need to be compiled >> with the -g option to GCC. It could of course be a compiler bug. >> Possibly compilation with a lower optimisation level would make it >> disappear. >> >> Bill. > > Bill, > > Do you know if the zn_poly test suite uses any random numbers?
Pseudorandom. The test in question uses both mpn_random2 and gmp_urandomm_ui. > If so, > does it use a random time-dependent seed, No. Not as far as I can tell. The initialisation in zn_poly 0.9 is just gmp_randinit_default (randstate). (Note mpn_random2 uses an internal GMP/MPIR state, not the provided state.) > and if so, does it print out > that seed? I don't see any in the trace below and I didn't find any in the code. > > -- William Bill. > >> >> On Apr 3, 6:00 am, "Dr. David Kirkby" <david.kir...@onetel.net> wrote: >>> I've built Sage tons of time on OpenSolaris as a 32-bit application, and >>> rarely >>> had any problems for the last 6 months or so. In fact, I've built >>> sage-4.7.alpha3 several times without issue. >>> >>> znpoly is a slightly unusual .spkg in Sage, in that it runs a minimal test >>> suite >>> irrespective of the setting of SAGE_CHECK. If SAGE_CHECK is set to "yes" >>> then it >>> runs a more comprehensive set of tests. >>> >>> But today with the sage-4.7.alpha3 I got a totally unexpected failure. >>> >>> gcc -g -g -fPIC -O3 -L. >>> -I/export/home/drkirkby/newdocs/sage-4.7.alpha3/local/include -I./include >>> -DDEBUG -o test/support-DEBUG.o -c test/support.c >>> gcc -g -o test/test src/array-DEBUG.o src/invert-DEBUG.o >>> src/ks_support-DEBUG.o >>> src/mulmid-DEBUG.o src/mulmid_ks-DEBUG.o src/misc-DEBUG.o >>> src/mpn_mulmid-DEBUG.o >>> src/mul-DEBUG.o src/mul_fft-DEBUG.o src/mul_fft_dft-DEBUG.o >>> src/mul_ks-DEBUG.o >>> src/nuss-DEBUG.o src/pack-DEBUG.o src/pmf-DEBUG.o src/pmfvec_fft-DEBUG.o >>> src/tuning-DEBUG.o src/zn_mod-DEBUG.o test/test-DEBUG.o test/ref_mul-DEBUG.o >>> test/invert-test-DEBUG.o test/pmfvec_fft-test-DEBUG.o >>> test/mulmid_ks-test-DEBUG.o test/mpn_mulmid-test-DEBUG.o >>> test/mul_fft-test-DEBUG.o test/mul_ks-test-DEBUG.o test/nuss-test-DEBUG.o >>> test/pack-test-DEBUG.o test/support-DEBUG.o >>> -L/export/home/drkirkby/newdocs/sage-4.7.alpha3/local/lib -lgmp -lm >>> test/test -quick all >>> mpn_smp_basecase()... ok >>> mpn_smp_kara()... make[2]: *** [check] Segmentation Fault (core dumped) >>> make[2]: Leaving directory >>> `/export/home/drkirkby/newdocs/sage-4.7.alpha3/spkg/build/zn_poly-0.9.p5/sr >>> c' >>> Error running zn_poly's quick test suite (make check). >>> >>> real 5m41.143s >>> user 1m8.034s >>> sys 0m5.595s >>> sage: An error occurred while installing zn_poly-0.9.p5 >>> >>> After I typed "make again" I see: >>> >>> Successfully installed zn_poly-0.9.p5 >>> >>> So for some unknown reason, znpoly has failed to pass the self-tests, when >>> I've >>> probably built it 100 times before and it passed each time. >>> >>> As usual, I checked the system log and see nothing to indicate the system >>> had a >>> problem like a memory error, disk error, lack of swap space etc. >>> >>> Dave >> >> -- >> 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 >> > > > > -- > William Stein > Professor of Mathematics > University of Washington > http://wstein.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
