From: Alan W. I. <ir...@be...> - 2002-11-27 18:09:45
|
On Wed, 27 Nov 2002, [iso-8859-1] Jo=E3o Cardoso wrote: > Are these the only memory leaks? They are very modest... 48 bytes... > Some leaks are expected, as for example when one duplicates a string or > open a new plot/device. > > In unix if we use 'valgrind' we also find leaks, but they are static, > i.e., they dont increasing with program complexity or looping. > As a matter of fact 'valgrind' finds more leaks in system libraries such > as X11 than in plplot: It has become a point of pride that KDE went through all its code to get ri= d of memory leaks found by valgrind so I suspect that developers for XFree86 and some of the other Linux system libraries will soon follow. It would be a nice point of pride with us as well. In a prior post to this list I documented every PLplot leak found by valgrind. See http://sourceforge.net/mailarchive/message.php?msg_id=3D1785861. To fix th= ese should be straightforward so I strongly encourage somebody with a good understanding of plplot initialization and termination to take up this challenge. Once PLplot has a clean bill of health from valgrind, it will be most interesting to see whether the windows debugger still finds memory leaks (and whether they are associated with PLplot or the windows libraries that it uses). Alan email: ir...@be... phone: 250-727-2902=09FAX: 250-721-7715 snail-mail: Dr. Alan W. Irwin Department of Physics and Astronomy, University of Victoria, P.O. Box 3055, Victoria, British Columbia, Canada, V8W 3P6 __________________________ Linux-powered astrophysics __________________________ |