On 23 Feb., 18:53, mabshoff <mabsh...@googlemail.com> wrote:
> On Feb 23, 4:42 am, mabshoff <mabsh...@googlemail.com> wrote:
>
> > Hi Georg,
>
> > here is the result of Sage 3.3 + your spkg patch for 64 bit. This is
> > compiled using --with-malloc=system:
>
> Ok, it turns out the failures I listed here are caused by oMalloc, but
> they are not caused by Georg's patch. They are also identical
> regardless if I use --with-malloc=system or Georg's second patch. I
> build a 32 bit 3.3 build on OSX and all tests pass with -long, so very
> nice work indeed. I will now take the spkg and run valgrind over all
> doctests on Linux to see if I can scare something else out. Should I
> fail again at this final task to poke a hole in George's patch it will
> be merged into Sage 3.4.alpha0 tonight :)
>
> The remaining issues for the 64 bit OSX build certainly seem rather
> strange failures and are deep inside oMalloc, so the whole commentary
> about the minpoly issue is likely a wrong lead. The strange thing is
> also that I can reproducibly segfault doctests at the exact same spot,
> but the failures occur with different commands and if I paste failing
> doctests directly into an interactive Sage session they pass. Since
> valgrind is available on OSX 10.5 Intel I will get it out of
> valgrind's CVS in the next couple days and start to investigate.
>
> Cheers,
>
> Michael
Hi Michael,
I could not put that much effort into it yesterday evening, but one
overnight complete build & testlong of Sage 3.3 with a
"singular...p3a.spkg" dropped in instead of the original "p3" one did
go through flawlessly. So either the #4181 patch (malloc=system) made
the minpoly issue go away again if it had been introduced by the #5344
patch (remove potential "four double free" problem), or the minpoly
issue is not introduced by it resp. does not occur at all with my
setting (32 Bit OS X 10.4.11).
Cheers,
gsw
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to
sage-devel-unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
