From 598965a6061e7c6d6adadf104c84bc7cd6cdeb07 Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Fri, 23 Dec 2005 23:22:23 +0000 Subject: clarified that curl_global_init() isn't thread-safe and that it might affect curl_easy_init() if you don't call curl_global_init() explicitly in your app --- docs/libcurl/curl_easy_init.3 | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'docs/libcurl/curl_easy_init.3') diff --git a/docs/libcurl/curl_easy_init.3 b/docs/libcurl/curl_easy_init.3 index 62a6fbc50..a9fbe792a 100644 --- a/docs/libcurl/curl_easy_init.3 +++ b/docs/libcurl/curl_easy_init.3 @@ -14,6 +14,12 @@ handle that you must use as input to other easy-functions. curl_easy_init initializes curl and this call \fBMUST\fP have a corresponding call to \fIcurl_easy_cleanup(3)\fP when the operation is complete. +If you did not already call \fIcurl_global_init(3)\fP, it will be done +automatically with a default setup when you call \fIcurl_easy_init(3)\fP. +This may be lethal in multi-threaded cases, since \fIcurl_global_init(3)\fP is +not thread-safe and must not be called more than once (or from more than one +thread). You are strongly adviced to not rely on this automatic behaviour, but +call \fIcurl_global_init(3)\fP yourself properly. .SH RETURN VALUE If this function returns NULL, something went wrong and you cannot use the other curl functions. -- cgit v1.2.3