On 04/ 4/11 01:01 PM, Bill Hart wrote:
Is the problem reproducible?
I'll have to check how reproducible it is by building znpoly repeatedly. But it's the first failure I've known in what must be more than 100 compete builds of Sage on this machine.
znpoly is only taking 39 s to build and run the short test suite, so if I run it for a day, I can build+test it 2200 times. The more comprehensive test suite takes several minutes.
But I've built Sage on this machine perhaps 100 times now, and the buildbot uses it too. So far only one failure.
If so, a valgrind log would be useful to debug the problem.
Valgrind is not supported on this operating system.
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.
It could be. Whatever it is, it a rare failure, though just how rare I don't know now. The program is compiled with -O3, so plenty of scope for reducing that.
The package compiles without any warnings at all, though the -Wall option is not added.
Had parallel builds been enabled in the package, I might have put it down to a race condition, but they are not, so it can't be that.
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
