From: Gutjahr, Troy <Troy.Gutjahr_at_tellabs.com>
Date: Fri, 14 Sep 2007 13:35:40 -0500

I have used libumem (http://access1.sun.com/techarticles/libumem.html)
on Solaris to find leaks and corruption in my application. I found a
couple of problems in libssh2 that we subsequently fixed in
libssh2-0.15. My application only exercises a small subset of the
library (retrieving files via sftp), so there might be similar problems
elsewhere in the library that have not been found yet.

-- Troy

-----Original Message-----
From: libssh2-devel-bounces_at_lists.sourceforge.net
[mailto:libssh2-devel-bounces_at_lists.sourceforge.net] On Behalf Of Daniel
Stenberg
Sent: Thursday, September 13, 2007 3:16 AM
To: roberto pulvirenti
Cc: libssh2 hacking; antonio.parlato.ext_at_nsn.com
Subject: Re: [libssh2] looking for memory leak

On Thu, 13 Sep 2007, roberto pulvirenti wrote:

> Have you ever used valgrind or any other similar tool for detecting
> memory leak on the last release of libssh2?

Yes. I've used valgrind on it on occasion.

> Your experience, if positive (even if on other operating
> system/compiler), could give me enough confidence that libssh2 is a
good choice.

libssh2 is still not very widely used and lots of changes have been done
in it during the last year so there's of course a risk that there are
remaining problems and leaks in there. The library has a rather
extensive API so various applications are likely to use it in new and
different ways that might provoke different problems.

But as this is open source, everyone is free and invited to dive in and
fix and improve.

------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft Defy all challenges.
Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
libssh2-devel mailing list
libssh2-devel_at_lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
============================================================
The information contained in this message may be privileged
and confidential and protected from disclosure. If the reader
of this message is not the intended recipient, or an employee
or agent responsible for delivering this message to the
intended recipient, you are hereby notified that any reproduction,
dissemination or distribution of this communication is strictly
prohibited. If you have received this communication in error,
please notify us immediately by replying to the message and
deleting it from your computer. Thank you. Tellabs
============================================================