New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl_easy_duphandle() bug after 7.69.1 #5097
Comments
Can you provide a simple stand-alone example code showing this problem? Both the tools you refer to above are huge and complex applications that make things really hard to debug or even understand what they're doing. |
Sorry, I'm afraid that I can't. |
My guess is correct. but reset to c8f086b , it's broken.. Sorry that I could not get more information. |
I still can't see what's wrong in there... |
cure the symptoms, not the disease -- temporary fix More infomation visit: curl/curl#5097
- Ignore CURLE_NOT_BUILT_IN errors returned by c-ares functions in curl_easy_duphandle. Prior to this change if c-ares was used as the resolver backend and either it was too old or libcurl was built without IPv6 support then some of our resolver functions could return CURLE_NOT_BUILT_IN to curl_easy_duphandle causing it to fail. Caused by c8f086b which shipped in 7.69.1. Reported-by: Karl Chen Fixes curl#5097 Closes #xxxx
If c-ares is too old or IPv6 support is disabled (like is the case here) those functions could return CURLE_NOT_BUILT_IN: Lines 788 to 812 in b81e0b0
I don't know for sure this is the problem but I don't see what else it could be. #5100 should fix this, @kn007 can you please try it? |
Ok, let me try it, wait a minute. my c-ares is 1.16.0, IPv6 is disabled. |
But why is the build IPv6-disabled, no such configure option was shown? |
I don't know.
Some people like me, will change it on the sysctl.conf file. |
Thanks |
To whom it may concern, the one off patch has already been applied to the FreeBSD Ports system: https://svnweb.freebsd.org/changeset/ports/530365 |
I try it on 7.69.1 and 7.69.2-dev, same problem. 7.69.0 working well.
dnf:
git:
The text was updated successfully, but these errors were encountered: