On Tue, 31 Mar 2009, Dan Fandrich wrote:
[CC'ed over to the libcurl list as this is now more libcurl than libssh2]
> On Tue, Mar 31, 2009 at 10:16:44AM -0400, Daniel Johnson wrote:
>> I did notice that the libssh2-related tests explicitly disable valgrind
>> use, so it wouldn't have helped in thi
On Tue, Mar 31, 2009 at 10:16:44AM -0400, Daniel Johnson wrote:
> I did notice that the libssh2-related tests explicitly disable valgrind
> use, so it wouldn't have helped in this case.
That was to avoid the OpenSSL false positives that result with the
OpenSSL-using tests. Those explicit disable
On Mar 30, 2009, at 4:39 AM, Daniel Stenberg wrote:
On Mon, 30 Mar 2009, Simon Josefsson wrote:
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-
On Mon, 30 Mar 2009, Neil Gierman wrote:
>> Like with http://dmalloc.com or similar? That looks like a fine lib to work
>> with for our use case...
>
> Does the Creative Commons Share Alike 3.0 license alter the licensing that
> libssh2 uses?
That's not a problem.
First because we don't intend
> Does anyone have any positive experience with something existing to
> share?
> Like with http://dmalloc.com or similar? That looks like a fine lib to
> work
> with for our use case...
>
Does the Creative Commons Share Alike 3.0 license alter the licensing that
libssh2 uses? The concern is the "
On Mon, 30 Mar 2009, Simon Josefsson wrote:
>> A) valgrind slows down the execution a lot. I can get the leak to occur in
>> my
>> tests but it seems virtually impossible to make happen when valgrind
>> monitors/slows down the code. A plain memory-leak detection would be
>> almos
Daniel Stenberg writes:
> On Mon, 30 Mar 2009, Simon Josefsson wrote:
>
>> 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
>> u
On Mon, 30 Mar 2009, Simon Josefsson wrote:
> 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 va
Daniel Stenberg writes:
> On Sun, 29 Mar 2009, Dan Fandrich wrote:
>
>>> Does anyone have any positive experience with something existing to share?
>>> Like with http://dmalloc.com or similar? That looks like a fine lib to work
>>> with for our use case...
>>
>> I've played with glibc's mtrace
On Sun, 29 Mar 2009, Dan Fandrich wrote:
>> Does anyone have any positive experience with something existing to share?
>> Like with http://dmalloc.com 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 s
On Mon, Mar 30, 2009 at 12:09:00AM +0200, Daniel Stenberg wrote:
> In order to help us track memory leaks etc in a useful manner, and perhaps
> especially on platforms without valgrind, I think we should consider
> implementing or using some kind of memory debugging system.
>
> Does anyone have
Daniel Stenberg wrote:
> Does anyone have any positive experience with something existing
> to share?
Only valgrind I'm afraid.
//Peter
--
___
libssh2-devel mailing list
libss
Hey
In order to help us track memory leaks etc in a useful manner, and perhaps
especially on platforms without valgrind, I think we should consider
implementing or using some kind of memory debugging system.
Does anyone have any positive experience with something existing to share?
Like with h
13 matches
Mail list logo
