[Kstars-devel] We've got a leak

[Jason Harris]

Ok, dumb question: how do I use calltree/kcachegrind to find memory leaks?  I 
have run kstars through calltree (using a greatly reduced data set to reduce 
execution time), but the nothing in the output made it obvious that a leak 
had been found.  KCachegrind looks really cool, but it seems to be geared 
toward optimization rather than debugging; does it present any information on 
bad memory usage?

I can post the calltree output file, if anyone is interested.

thanks,
Jason

On Friday 03 October 2003 08:24 am, Jason Harris wrote:
> Hello,
>
> Just got this bug report:
> http://bugs.kde.org/show_bug.cgi?id=65413
>
> I've just confirmed it by monitoring memory usage over ~20 minutes.
> It's gone up from 112 MB to 121 MB.
>
> :(
>
> Jason

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