Has anyone been running gaim from svn lately with valgrind?
I would like to know why gaim svn needs so much memory to run but I can
not find the source of the problem.
There seems to be small memory leaks but they should not cause any mayor
It seems memory consumption grows too much over time and I do not know
if the problem is just heap fragmentation or maybe gaim is missusing
memory in some way.
What tool do you recommend to analyze memory usage?
From: Jason Spiro <jasonspiro4+news@gm...> - 2006-06-16 20:23:57
On 2006-06-04, Eduardo Pérez <eperez@...> wrote:
> What tool do you recommend to analyze memory usage?
For detecting memory leaks, when doing school assignments, I use
valgrind. Valgrind is the standard. Everyone uses it.
That said, I used to use mudflap. IIRC, it's faster but its checks are
less complete than Valgrind's. To use it, IIRC, in Debian:
apt-get install libmudflap0
gcc hello.c -o hello -fmudflap
There are also ways to use mudflap with multi-source-file executables.
You'll want to set the mudflap options. To see them, use:
I used to use: MUDFLAP_OPTIONS='-internal-checking -print-leaks
P.S. There are other memory leak checkers, search at freshmeat.net for:
I'd be curious if you emailed me to let me know how it goes.
On Fri, 2006-06-16 at 20:23 +0000, Jason Spiro wrote:
> P.S. There are other memory leak checkers, search at freshmeat.net for:
> memory leak
Has anyone tried google's performance tool
(http://goog-perftools.sourceforge.net/doc/heap_checker.html )? I've
used it briefly at work, the initial impression is that it's a lot
faster than valgrind. It's text output is crap though, as far as I know
you have to look into the postscript output for callstack.