curl/curl
1
1
Fork 0
mirror of https://github.com/curl/curl.git synced 2025-09-16 17:12:43 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: curl_version_info is not thread-safe before libcurl initialization

Browse Source 
Closes #9583
This commit is contained in:
Patrick Monnerat 2022-09-25 17:30:23 +02:00 committed by Daniel Stenberg
parent e780aae77a
commit e1e482517f
No known key found for this signature in database
GPG Key ID: 5CC908FDB71E12C2
2 changed files with 6 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/libcurl/curl_version_info.3
View File

@ -46,6 +46,10 @@ Applications should use this information to judge if things are possible to do
or not, instead of using compile-time checks, as dynamic/DLL libraries can be or not, instead of using compile-time checks, as dynamic/DLL libraries can be
changed independent of applications. changed independent of applications.
This function can alter the returned static data as long as
\fIcurl_global_init\fP has not been called. It is therefore not thread-safe
before libcurl initialization occurs.
The curl_version_info_data struct looks like this The curl_version_info_data struct looks like this
.nf .nf

2
docs/libcurl/libcurl-thread.3
View File

@ -111,3 +111,5 @@ replacements, must be thread safe. You can use \fIcurl_global_init_mem(3)\fP
to set your own replacement memory functions. to set your own replacement memory functions.
.IP "Non-safe functions" .IP "Non-safe functions"
\fICURLOPT_DNS_USE_GLOBAL_CACHE(3)\fP is not thread-safe. \fICURLOPT_DNS_USE_GLOBAL_CACHE(3)\fP is not thread-safe.
\fIcurl_version_info(3)\fP is not thread-safe before libcurl initialization.