And the valgrind issue goes away if we link the pbori.pyx statically with libpolybori.a,libpboriCudd.a and libgroebner.a. To do that delete all ibpolybori*[so|dylib]*,libpboriCudd.*[so|dylib]* and libgroebner.*[so|dylib]* and then rebuild sage/rings/polynomial/ pbori.pyx. Then the error is gone:
==10612== Using valgrind-3.3.0, a dynamic binary instrumentation framework. ==10612== Copyright (C) 2000-2007, and GNU GPL'd, by Julian Seward et al. ==10612== For more details, rerun with: -v ==10612== ==10612== My PID = 10612, parent PID = 10602. Prog and args are: ==10612== /scratch/mabshoff/release-cycle/sage-3.1.2.rc0/local/bin/ python ==10612== /scratch/mabshoff/release-cycle/sage-3.1.2.rc0/ tmp/.doctest_wrapper_parent.py ==10612== --10612-- DWARF2 CFI reader: unhandled CFI instruction 0:10 --10612-- DWARF2 CFI reader: unhandled CFI instruction 0:10 ==10612== ==10612== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 579 from 2) ==10612== malloc/free: in use at exit: 32,775,076 bytes in 198,627 blocks. ==10612== malloc/free: 856,889 allocs, 658,262 frees, 193,257,771 bytes allocated. ==10612== For counts of detected errors, rerun with: -v ==10612== searching for pointers to 198,627 not-freed blocks. ==10612== checked 38,913,672 bytes. We used to do the same thing with PolyBoRi 0.3.x, so readding it to the 0.5.rc1.spkg will also work around the issue for now. Cheers, Michael --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
