Hi David, On 2012-12-20, David Kirkby <david.kir...@onetel.net> wrote: > I've compiled Sage on Solaris with Sun libraries which replace > malloc/free with versions which check for memory leaks. Sage has > leaked memory before the > > sage: > > prompt has appeared. But from what I gather, one of the culprits does > it own memory management, which would not be detected by those > libraries.
That sounds like libsingular. Can you try to install the singular spkg from #13731, after doing export SINGULAR_XALLOC=yes followed by sage -b, please? This will result in (lib)Singular being built with xalloc (a thin compatibility layer on top of malloc) replacing Singular's usual memory manager omalloc. Moreover, the spkg backports a couple of upstream fixes for out-of-bound errors detected by Sage's doctests run with export MALLOC_CHECK_=3 using Singular with xalloc. 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.
