[Kstars-devel] We've got a leak

[Jason Harris]

Nevermind, my mistake was thinking that calltree does the same thing valgrind 
does. AFAICT, calltree is for optimizing only, for memory errors use valgrind 
like this:

% valgrind --leak-check=yes --leak-resolution=high kstars

I believe the leaks have been found and fixed, thanks to the bug reporter.  
CVS log coming shortly.

regards,
Jason

-- 
KStars:  A K Desktop Planetarium
http://edu.kde.org/kstars