On Thu, 29 May 2003, Paul Accosta wrote:

> Ive pretty much combed the entire program and used Purify to make sure
> there is no memory leaks on my part. I do a check by getting the memroy
> before these series of calls and then get a check of memory after clean_up
> and it is still higher.

But... if you have Purify and can use that, why can't you just use it and see
if libcurl leaks anything or not? (I haven't ever used that myself.)

I'm pretty confident that libcurl doesn't leak anything in most "normal"
cases, as I always run the test suite with full memory leak detection
enabled, but there might of course exist corner-cases that we haven't added
to the test suite and thus remain undetected.

> The program never terminitnates so I do not use curl_global_cleanup.

You shouldn't get any leaks because of that.

> Im not sure what else I can do, any ideas?

Have you read the lib/README.memoryleak document?

Oh, and make sure that you use a recent version of libcurl.

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5