On Thursday, July 28, 2016 at 8:29:13 AM UTC-7, leif wrote: > > Jean-Pierre Flori wrote: > > And at some point I had to disable omGetBackTrace: > > https://trac.sagemath.org/ticket/15679 > > IIRC there's also some OM_DEBUG (or OM_NDEBUG?) preprocessor constant > you could toggle. (Perhaps it's even a debug /level/.)
See also https://trac.sagemath.org/ticket/13731 for some hints on memory debugging in singular. At one point we succeeded in building singular with "xalloc" rather than "omalloc", which has the advantage that normal memory debugging tools (such a valgrind, electric fence, etc.) work for it. With a little luck you can get all this by just setting SAGE_DEBUG=yes when you build singular, but I'd expect that it has bitrotted by now and would need some loving attention to get it working again. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
