Download
Browse source Changelog
Documentation
Project   Bug Bounty   Help us   Known bugs   TODO Protocols   CA bundle   HTTP Cookies   HTTP/2   SSL Certs Releases   Security   Version numbers   Vulnerabilities curl tool   man page   Tutorial   HTTP scripting Who and Why
libcurl
ABI API Competitors Examples Features Mailing list Related libs Using libcurl Tutorial Testimonials
Get Help
curl-library curl-users Mailing lists Book: Everything curl Video presentations Report a bug Paid support
Development
Autobuilds Code Style Contribute Deprecate Internals Release Notes Release Procedure Roadmap Run Tests Security Process Specifications Test curl
News
Changelog Release table
curl / Mailing Lists / curl-library / 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: Help: libcurl debug

From: Kunal Chauhan via curl-library <curl-library_at_cool.haxx.se>
Date: Sat, 16 May 2020 22:56:14 +0530

Hi Team,

*1. Below is my curl version is it old m I am using it , Still I have
checked all code seems fine at application end which is feeding to CURL .
it seems "curl_perform" is causing issue which is str len. please suggest !*

curl --version
curl 7.55.0 (arm-unknown-linux-gnueabi) libcurl/7.55.0 OpenSSL/1.0.2j
zlib/1.2.8 libssh2/1.2.4
Release-Date: 2017-08-09
Protocols: file ftp ftps http https scp sftp
Features: IPv6 Largefile NTLM SSL libz TLS-SRP UnixSockets HTTPS-proxy

On Fri, May 15, 2020 at 3:22 AM Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Fri, 15 May 2020, Kunal Chauhan wrote:
>
> > my curl version is : 7.35.0
>
> 1. Please stop top-posting. It makes this very hard to read and follow and
> as YOU have the problem, you should strive to make OUR reading
> experience easier and faster.
>
> 2. Your libcurl is very old and has lots of known vulnerabilities. You
> will be
> better off by upgrading to a modern version before wasting time
> looking to
> fix a problem which *might* be a libcurl problem we fixed 6 years ago.
>
> 3. Build your code with debug symbols (-g on with gcc or clang) so that you
> get told exact line numbers and variable contents for stack frames.
> When
> you get problems *inside* libcurl, a good advice is to also build a
> version
> of curl with debug symbols present as then you can get a fully detailed
> stack trace.
>
> 4. If you still experience problems you can't find: write a small
> stand-alone
> example code that reproduces the problem and show us. Then we can build
> that, reproduce the problem and help figuring out what to do to fix it.
>
> If you *can't* write a small program that reproduces the issue, that's
> a
> rather strong indication the problem is not in libcurl...
>
> --
>
> / daniel.haxx.se | Commercial curl support up to 24x7 is available!
> | Private help, bug fixes, support, ports, new features
> | https://www.wolfssl.com/contact/
> 

-- 
*Thanks with Regards!*
*Kunal Chauhan*
*Mob:09813614826*
*Mob:08860397903*
*E-mail:atkunalchauhan_at_gmail.com <E-mail%3Aatkunalchauhan_at_gmail.com>*

-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2020-05-16