cURL / Mailing Lists / curl-users / Single Mail

curl-users

Re: Memory leak problem "still reachable: 288 bytes in 8 blocks."

From: Daniel Stenberg <daniel_at_haxx.se>
Date: Tue, 23 Dec 2008 13:54:40 +0100 (CET)

On Tue, 23 Dec 2008, rajnivanza_at_gmail.com wrote:

> i have written simple program for testing curl example.

Then please use the curl-library mailing list!

> ==27282== at 0x40053C0: malloc (vg_replace_malloc.c:149)
> ==27282== by 0x7DF6C5D: (within /lib/libcrypto.so.0.9.8b)
> ==27282== by 0x7DF72DE: CRYPTO_malloc (in /lib/libcrypto.so.0.9.8b)
> ==27282== by 0x7E3A640: ENGINE_new (in /lib/libcrypto.so.0.9.8b)
> ==27282== by 0x7E3E5AB: ENGINE_load_dynamic (in /lib/libcrypto.so.0.9.8b)
> ==27282== by 0x7E3CB46: ENGINE_load_builtin_engines (in
> /lib/libcrypto.so.0.9.8b)

What libcurl version? Is that really OpenSSL 0.9.8b? That's rather old by
now...

Since the leak is clearly in a malloc done by OpenSSL, the question is of
course if libcurl calls the proper cleanup function OpenSSL provides as if it
does then the fault is not libcurl's but OpenSSL's. Still, I figure trying out
a recent OpenSSL first would be a good idea.

And as I said, take follow-ups on the more suitable mailing list...

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/cgi-bin/mailman/listinfo/curl-users
FAQ:        http://curl.haxx.se/docs/faq.html
Etiquette:  http://curl.haxx.se/mail/etiquette.html
Received on 2008-12-23