I'm not a Valgrind expert, but I think that it's the tool you're looking for. Take a look at the Valgrind options listed at the bottom of the output from "sage -advanced". sage -memcheck looks like it might be useful. David
On Wed, Nov 23, 2011 at 13:12, Dima Pasechnik <dimp...@gmail.com> wrote: > consider the following Sage code: > while True: > reset() > # do some time– and memory-consuming stuff (using mpmath) > When it is run, we witness at each iteration the amount of memory growing, > until, after 10 hours or so, it takes 3Gb of RAM > and triggers an OOM kernel event... > Is it a memory leak? > How one does debug this? > Thanks, > Dima > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
