Re: Memory allocation issues with libcurl on solaris
Date: Thu, 30 Jan 2020 15:16:12 +0000
Thank you Daniel
This is the version of curl
curl 7.68.0 (sparc-sun-solaris2.10) libcurl/7.68.0 OpenSSL/1.0.1g zlib/1.2.3
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
Features: AsynchDNS Debug HTTPS-proxy IPv6 Largefile libz NTLM NTLM_WB SSL TLS-SRP TrackMemory UnixSockets
On 1/30/20, 7:04 AM, "Daniel Stenberg" <daniel_at_haxx.se> wrote:
CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
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 libcurl.so.4.6.0
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
https://urldefense.proofpoint.com/v2/url?u=https-3A__curl.haxx.se_libcurl_c_example.html&d=DwIBAg&c=HhgxO5mnlCoNHjwVH-wED6Mwc4Z-psO9z_38k9ow5oI&r=aKh9QCNQ8OtZc4DT1WWdDtTf-ZLlP34_mbJvsqfurQ8&m=Yg49Ttdup2KxAddebepS8glo3erWg3Qb28BfIzUfznU&s=jxd6KIcq7lkL9BWvpFplcodpCHlkfOuNrHcuRmSNP3Y&e= - 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
/ daniel.haxx.se | Commercial curl support up to 24x7 is available!
| Private help, bug fixes, support, ports, new features
The information contained in this message and any accompanying attachments may contain privileged, private and/or confidential information protected by state and federal law. Penalties may be assessed for unauthorized use and/or disclosure. This message and any attachments are intended for the designated recipient only. If you have received this information in error, please notify the sender immediately and return or destroy the information.
This e-mail transmission and any attachments are believed to have been sent free of any virus or other defect that might affect any computer system into which it is received and opened. It is, however, the recipient's responsibility to ensure that the e-mail transmission and any attachments are virus free, and the sender accepts no responsibility for any damage that may in any way arise from their use.