Thank you . Yes, I will update the system to the latest libcurl as soon as possible and do a full review of the code.
Normally these kind of errors appear in multithreaded environments when you update shared variables without ensuring proper atomicity. Have a nice day On November 30, 2023 11:10:17 PM GMT+01:00, Daniel Stenberg via curl-library <[email protected]> wrote: >On Thu, 30 Nov 2023, [email protected] wrote: > >> I do not understand how I pass _URL to setopt() who does its strdup thing >> and then later on this strduped memory area is separated into a correct HOST >> and not correct GET location. > >No one understands that. Because that's not how it should work and that is not >how it has behaved for countless previous transfers. > >> Any more ideas? > >Words and explanations are good but they basically cannot replace an actual >reproducible appliction source code. And only you know how your application >works to a detail sufficient to be able to write such a reproducible. After >all, we have not confirmed that problem you see actually is in libcurl. > >It also always makes sense to build and test with the latest libcurl before >spending too much time on debugging, just to make sure that this is not a >problem that is already gone there. The official count says we fixed 1369 bugs >between 7.85.0 and 8.4.0! > >-- > > / daniel.haxx.se > | Commercial curl support up to 24x7 is available! > | Private help, bug fixes, support, ports, new features > | https://curl.se/support.html >-- >Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library >Etiquette: https://curl.se/mail/etiquette.html
-- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
