Subject: Re: memory (leak) debugging

Re: memory (leak) debugging

From: Simon Josefsson <>
Date: Mon, 30 Mar 2009 10:29:56 +0200

Daniel Stenberg <> writes:

> On Sun, 29 Mar 2009, Dan Fandrich wrote:
>>> Does anyone have any positive experience with something existing to share?
>>> Like with or similar? That looks like a fine lib to work
>>> with for our use case...
>> I've played with glibc's mtrace a bit. It's pretty basic, but it seems to
>> give about the same level of capability as libcurl's memdebug subsystem.
> I'd rather not see it depdend on glibc though, since it's not that widely used
> (on non-Linux).
> I'll proceed with dmalloc for now and see if that turns out good enough.

I gave up on dmalloc a long time ago, in my experience valgrind leads to
better results and doesn't require changes to the build.

In most of my other projects, I always set up so that the self-tests are
run under valgrind automatically (if valgrind is installed). Maybe that
would help libssh2? We need more self-tests, though...


libssh2-devel mailing list
Received on 2009-03-30