On Mon, 4 Jun 2018, Martin Galvan wrote:
Yeah, that would make more sense, but I'd hope the docs would be a bit more
explicit about it. Is there a chance of libcurl needing this to be alive
after calling curl_easy_perform?
The docs say that: "libcurl will need it until you call
2018-06-04 18:09 GMT-03:00 Rich Gray :
> I believe it means don't do things like set it to an automatic variable in a
> function and then call libcurl after exiting the function. Don't point it
> at malloc'd space and then call libcurl after freeing said space, etc.
>
> Rich
Yeah, that would
Martin Galvan wrote:
Hi all,
The CURLOPT_ERRORBUFFER docs say:
"You must keep the associated buffer available until libcurl no longer
needs it. Failing to do so will cause very odd behavior or even crashes.
libcurl will need it until you call curl_easy_cleanup or you set the same
option again
Hi all,
The CURLOPT_ERRORBUFFER docs say:
"You must keep the associated buffer available until libcurl no longer
needs it. Failing to do so will cause very odd behavior or even crashes.
libcurl will need it until you call curl_easy_cleanup or you set the same
option again to use a different
