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: Periodic segfault in curl_easy_perform()
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Daniel Stenberg via curl-library <curl-library_at_cool.haxx.se>
Date: Wed, 10 Feb 2021 15:42:13 +0100 (CET)
On Wed, 10 Feb 2021, Adrián Gimeno Balaguer via curl-library wrote:
> The program crashes after 5-10 minutes since startup (provided the periodic
> check always sends files) at curl_easy_perform() with the following stack
> trace:
As Tomalak mentioned, we can't do a lot if we cannot reproduce this problem. A
lot of users run libcurl and nobody else has reported this problem before.
Some debugging ideas:
- If you build libcurl debug enabled (with -g) you might get more details in
the stack trace from the crash, which might help.
- If you run with gdb and catch the crash, it might help to inspect local
variables and the stack trace.
- Try building your application with memory/address sanitizers or run with
valgrind to catch mistakes in your code that could be what makes libcurl trip.
> libcurl/7.74.0-DEV
I trust you built this from a release tag and it isn't just a random commit
from the middle of the release cycle? The "-DEV" part there reveals it isn't
from a release package.
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-02-10
Date: Wed, 10 Feb 2021 15:42:13 +0100 (CET)
On Wed, 10 Feb 2021, Adrián Gimeno Balaguer via curl-library wrote:
> The program crashes after 5-10 minutes since startup (provided the periodic
> check always sends files) at curl_easy_perform() with the following stack
> trace:
As Tomalak mentioned, we can't do a lot if we cannot reproduce this problem. A
lot of users run libcurl and nobody else has reported this problem before.
Some debugging ideas:
- If you build libcurl debug enabled (with -g) you might get more details in
the stack trace from the crash, which might help.
- If you run with gdb and catch the crash, it might help to inspect local
variables and the stack trace.
- Try building your application with memory/address sanitizers or run with
valgrind to catch mistakes in your code that could be what makes libcurl trip.
> libcurl/7.74.0-DEV
I trust you built this from a release tag and it isn't just a random commit
from the middle of the release cycle? The "-DEV" part there reveals it isn't
from a release package.
-- / daniel.haxx.se | Commercial curl support up to 24x7 is available! | Private help, bug fixes, support, ports, new features | https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette: https://curl.se/mail/etiquette.html
Received on 2021-02-10