Personally, I'd recommend making valgrind builds separate from regular builds. The use case is, install Sage with this spkg with special build flags, so that you get a Sage good for valgrinding. I would suspect that this version compiles with -O0, for example.
On Wed, Jul 29, 2009 at 7:38 AM, Simon King<simon.k...@uni-jena.de> wrote: > > Hi! > > I installed the valgrind spkg, exported SAGE_VALGRIND="yes" and did > "sage -ba". Apparently it worked, because doing "sage -valgrind" now > gave me information about memory leaks and stuff. > > Is it correct that the above makes sage slower, even if I only do > "sage" and not "sage -valgrind"? > > If it is correct: How can I uninstall valgrind? I tried to do "sage - > ba" without SAGE_VALGRIND="yes". But still, when I start sage then a > valgrind process appears in the list of processes. Moreover, when I > start "top", sage appears as "memcheck" in, where it is usually called > "ipython". > > Do you recommend building Sage from scratch, or will there be no time > regression unless I use "sage -valgrind"? > > Cheers, > Simon > > > > -- Robert L. Miller http://www.rlmiller.org/ --~--~---------~--~----~------------~-------~--~----~ 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 For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
