On Sun, Jun 27, 2010 at 1:05 PM, Dr. David Kirkby <david.kir...@onetel.net> wrote: > On 06/27/10 08:55 PM, Robert Miller wrote: >> >> Feel free to put me in charge of the memleak component. > > Done. > > As a matter of interest, what techniques are you using for memory leak > testing? I assume valgrind is one, but are there others?
So far it's been mostly valgrinding the test suite. However, in the past I have also used the following technique to discover memory leaks: 1) Try to classify a massive amount of mathematical objects by running large computations on shared machines. 2) Get a lot of angry emails when the machine crashes. 3) Realize that this is because I've locked up all the memory unknowingly in my computations. 4) Hunt down the leaks. -- Robert L. Miller http://www.rlmiller.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
