Hi, Simon, > On Feb 12, 2019, at 12:24 , Simon King <simon.k...@uni-jena.de> wrote: > > Hi! > > Working at #27261, it seems to me that there is a memory leak somewhere > either in Sage's use of libsingular, or in libsingular internally. > > 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?
I can’t answer most of your questions, but for the last, internet search is your friend… <http://valgrind.org> appears to have much of what you need (except for the Sage connection :-}). HTH Justin -- Justin C. Walker, Curmudgeon at Large Director Institute for the Enhancement of the Director's Income ----------- If you don't know where you're going, you might wind up someplace else. - Yogi Berra -- -- 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.
