cURL / Mailing Lists / curl-library / Single Mail


RE: curl api nghttp2 co-req ?

From: Catlow, Martyn <>
Date: Fri, 11 Mar 2016 13:55:07 +0000

Hi there again.

Having overcome the co-req issues (below), I now have a good build of libcurl api which is working fine in a normal use case. However I need to implement the function that calls the api in slightly different way, it being fetched into memory at runtime then dynamically called (i.e dll like, but not a dll - this is the z/OS operating system which has a module fetch() pre-load function to overcome with certain inter language linkage constraints).

The curl api work fine when the function is statically linked and called, but when the function is loaded and called some of the curl calls appear to work, but curl_easy_perform() returns

"curl_easy_perform() failed: Out of memory"

Is there any way to diagnose where this failure is occurring in order to understand the circumstances ?

Code attached for reference.

M J Catlow - Portfolio Lead Centralised ICT Delivery
Met Office  Fitzroy Road, Exeter, Devon, EX1 3PB United Kingdom
Tel: +44(0)1392 884651 divert 07753 880517

-----Original Message-----
From: curl-library [] On Behalf Of Daniel Stenberg
Sent: 11 January 2016 12:25
To: libcurl development
Subject: RE: curl api nghttp2 co-req ?

On Mon, 11 Jan 2016, Catlow, Martyn wrote:

> I guess you refer to configure of the curl install itself rather than
> the api program build ? In which case I guess this needs pushing back
> to the third party who delivered the original curl build ?

Yes, when you build curl you build it with a set of 3rd party libs/dependencies and then you can choose to not build with HTTP/2 support.


List admin:

List admin:

Received on 2016-03-11