Hi! On #13731, Nils Bruin suggested to try and create a Singular spkg in which omalloc (Singular's usual memory manager) is replaced by malloc. That way, memory check tools can be used more easily (but Singular is slower, so, malloc shouldn't be the default).
Nils' idea was efficient: Several upstream bugs were found. See Sage ticket #13731 and Singular ticket #463. With the help of libsingular-devel, We created a new patchlevel of our Singular spkg. It contains backports of several upstream fixes, and it *optionally* replaces omalloc by xalloc (that's a compatibility layer for omalloc on top of malloc, and still allows to use debugging tools). On linux and with MALLOC_CHECK_=3, all tests except one unrelated problem in sage/graphs pass without crash. Hence, the new spkg at #13731 is ready for review. But wait a second: I just saw on libsingular-devel that some factorization problems were fixed upstream. Perhaps we could use the occasion and use #13731 for backporting these fixes as well? Or is it better to keep the fixes separate? Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. 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. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
