Hello,

FYI,
I found a test program on forum, attached is copy of it.
I ran this program on different platforms having GlibC and uClibC with
an invalid URL as parameter.
For GlibC it ran without any leaks, but for uClibC it kept on increasing
its memory size.

Let me see if I get any more pointers and I'll update you.

Regards,
Vikram.

On Mon, 2007-06-25 at 09:23 +0200, Daniel Stenberg wrote:
> On Mon, 25 Jun 2007, vikram wrote:
>
> > I was talking about the file created using curl_memdebug("dump"); I was not
> > able to get that file for your reference.
>
> Then I doubt the leak is made by libcurl...
>
> > FYI, I'm using uClibc, let me check whether it is reproducable on Glibc (to
> > check whether issues with gethostbyname_r()). I'll provide you code snippets
> > to reproduce it.
>
> Great. Did you try valgrind to pinpoint the leak?
>