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: core dump on curl function call

From: Daniel Stenberg via curl-library <>
Date: Thu, 30 Sep 2021 14:16:31 +0200 (CEST)

On Thu, 30 Sep 2021, treesa fairy joseph via curl-library wrote:

> Program terminated with signal SIGSEGV, Segmentation fault.
> #0 0x00000000004c3008 in singlesocket ()
> (gdb) bt
> #0 0x00000000004c3008 in singlesocket ()
> #1 0x00000000004c6ac8 in curl_multi_remove_handle ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)

I suggest you rebuild curl with debug symbols present so that the stack trace
becomes useable. Then you can investigate exactly what happned there in frame
0 and possibly why. Or at least tell us more details and we might be able to

I presume this is a recent libcurl? I'm not aware of any known flaw in that
function in recent time.

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