On Mon, 14 Mar 2016, Catlow, Martyn wrote:

Please don't top-post. It makes reading and following the context really hard.

> the run environment unfortunately doesn't allow for this to be interactively
> debugged.

Then I suggest printf sprinkling.

> I was hoping being an early failure it might be easy to figure from the
> source; is that a feasible approach ?

If it truly is an early failure, sure. The weird thing is that libcurl already
does memory allocations in curl_easy_init() so why does that work and not the
allocations done by curl_easy_perform()?

The first failure place where CURLE_OUT_OF_MEMORY can be returned from
curl_easy_perform is probably if Curl_multi_handle() fails (line
lib/easy.c:794 in current code).

> I have curl-7.47.2-20160314 but can't figure the module naming conventions.

Which module naming conventions do you mean?

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:  https://curl.haxx.se/mail/etiquette.html