On Tue, 25 May 2021, Ville Likitalo via curl-library wrote:
The only interesting bit in the stack trace is that the pointer
which gets passed to libc free(void*) is one that has been
allocated with the private malloc libcurl has been set up with.
Now, I could not quickly find any existing open or closed bug
that would describe this but would this already be fixed in the
later versions?
Without debug symbols nor any way to reproduce this problem, I don't think we
can tell for sure what the problem is or if it has been fixed already.
--
/ 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
