curl / Mailing Lists / curl-users / Single Mail
Buy commercial curl support from WolfSSL. We help you work out your issues, debug your libcurl applications, use the API, port to new platforms, add new features and more. With a team lead by the curl founder himself.

Re: Memory allocation issues with libcurl on solaris

From: Daniel Stenberg via curl-users <>
Date: Thu, 30 Jan 2020 15:04:28 +0100 (CET)

On Thu, 30 Jan 2020, Jitta, Machender wrote:

Please take this to the curl-library mailing list. You will reach *thousands*
of libcurl users and hackers there. Most of them are not on this mailing list.
You're not reaching the correct crowd here.

I'm going to CC this reply over to that list.

> Reading

This is not the version number, this is the SONAME. The ABI number basically.
It isn't specific enough.

curl -V will typically show the version number.

> - Call first API with headers after curl initialization
> - Reset curl
> - Prepare second API with headers. It fails while appending a header.

The devil is always in the details. Please show us an *exact* source code
example that causes problems. It sounds as if you've done some mistake that
libcurl didn't like/support.

We offer over a hundred examples over at - does any of them cause a crash
when you build and run it? If so, which?

And again: please subscribe to curl-library and continue this thread on that
list instead!

  / | Commercial curl support up to 24x7 is available!
                   | Private help, bug fixes, support, ports, new features
Received on 2020-01-30