On Fri, 29 Oct 2004, Brian Akins wrote:

> A pointer to a filled-in struct, or NULL if it failed or ran out of structs.
> It also writes the number of messages left in the queue (after this read) in
> the integer the second argument points to.
>
> Do I need to free this message? How do I ensure I don't "run out of
> structs"? I have a long running process that doesn't need to leak memory or
> run out of structs.

No, you must not free that message. When you call the function again, the
previous one will be gone and when calling cleanup.

I'm not aware of any memory leaks in the current libcurl.

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
       Dedicated custom curl help for hire: http://haxx.se/curl.html