Subject: Re: Memory leak...

Re: Memory leak...

From: Steinar H. Gunderson <sesse_at_google.com>
Date: Sun, 30 Sep 2007 00:52:08 +0200

On Sat, Sep 29, 2007 at 11:23:42PM +0200, Daniel Stenberg wrote:
> #1 - A fresh new memory leak, much clearly shown by curl's test case 20:
>
> ** MEMORY FAILURE
> Leak detected: memory still allocated: 55 bytes
> At 80f9534, there's 27 bytes.
> allocated by ares_gethostbyname.c:100
> At 80f9504, there's 28 bytes.
> allocated by ares_gethostbyname.c:93

I can't seem to reproduce this. ./configure --enable-static --disable-shared
--enable-ares (do I really have to "make install" in c-ares for this to
work?), and test 020 works fine, even in valgrind.

/* Steinar */

-- 
Software Engineer, Google Norway
Received on 2007-09-30