On Mar 28, 2009, at 9:54 AM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Fri, 27 Mar 2009, Daniel Johnson wrote:
>
>> Well, I'm not getting segfaults, but I'm still getting test failures:
>>
>> test 600...[SFTP retrieval]
>>
>> ** MEMORY FAILURE
>> Leak detected: memory still allocated: 188 bytes
>> At 30c264, there's 188 bytes.
>> allocated by ../../curl/lib/ssh.c:281
>>
>> which is in libcurl's LIBSSH2_ALLOC_FUNC.
>
> Hm, that leak is terribly annoying to catch (unless you run with
> valgrind). I
> saw it once and it turned out it was the 'sftpInit_sftp' handle
> allocated at
> sftp.c:621 but I couldn't figure out why.
>
> I don't get this problem much. I seem to get intermittent errors but
> I'm not
> entirely sure who's to blame and I've run the tests 600 to 637
> numerous times
> without failing as well.
Too bad there's no OS X port of valgrind yet.
The tests are failing consistantly for me and prior to the recent
changes to libssh2 they consistantly passed.
>
>
>> TESTFAIL: These test cases failed: 600 602 604 608 609 610 611 612
>> 613 614
>> 615 616 618 620 622 624 625 626 627 633 634 635 636 637 2004
>
> Do they all fail with this leak error?
>
> --
>
> / daniel.haxx.se
>
> ---
> ---
> ---
> ---------------------------------------------------------------------
> _______________________________________________
> libssh2-devel mailing list
> libssh2-devel_at_lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/libssh2-devel
Yes, I believe so. Unfortunately, I can't check right now since my
laptop seems to have one of those defective Nvidia chips and I have no
display. :p I won't have a replacement until Monday. After then I can
try to better debug things.
Daniel
------------------------------------------------------------------------------
_______________________________________________
libssh2-devel mailing list
libssh2-devel_at_lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libssh2-devel
Received on 2009-03-28