[sage-devel] Re: Valgrind - how to?
The ticket for upgrading valgrind is at https://trac.sagemath.org/ticket/19618 -- 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.
[sage-devel] Re: Valgrind - how to?
On Wednesday, February 13, 2019 at 8:44:07 AM UTC+1, Simon King wrote: > > Hi again, > > On 2019-02-12, Simon King > wrote: > > If I recall correctly, valgrind would be able to report leaking memory. > > But how to use it in Sage? > > > > I guess `sage -i valgrind` is the first step. But then? `make start`? > > `sage -ba`? Can you also point me to a valgrind tutorial that > > demonstrates how to use it to analyse a memory leak? > > It seems that with a debug build (`export SAGE_DEBUG=yes`), > `sage --valgrind` > pretty much does what I was looking for. > > I guess that it is the way to go. > Note that `sage -i valgrind` fails, so, the experimental valgrind > package is broken. But `sage --valgrind` apparently is able to use a > system-wide valgrind installation. > > Yes, I think nobody updated the valgrind package for a long time. Anyway uing the system wide one is surely a better idea. > Best regards, > Simon > > -- 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.
[sage-devel] Re: Valgrind - how to?
Hi again, On 2019-02-12, Simon King wrote: > If I recall correctly, valgrind would be able to report leaking memory. > But how to use it in Sage? > > I guess `sage -i valgrind` is the first step. But then? `make start`? > `sage -ba`? Can you also point me to a valgrind tutorial that > demonstrates how to use it to analyse a memory leak? It seems that with a debug build (`export SAGE_DEBUG=yes`), `sage --valgrind` pretty much does what I was looking for. Note that `sage -i valgrind` fails, so, the experimental valgrind package is broken. But `sage --valgrind` apparently is able to use a system-wide valgrind installation. Best regards, Simon -- 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.
