From 0da1f5dc5cf0ddf7aadbb713ee1291ef6fb6ede0 Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Fri, 31 Jul 2015 01:58:03 -0400 Subject: libcurl-thread.3: Warn memory functions must be thread safe Bug: http://curl.haxx.se/mail/lib-2015-07/0149.html Reported-by: Eric Ridge --- docs/libcurl/libcurl-thread.3 | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'docs/libcurl/libcurl-thread.3') diff --git a/docs/libcurl/libcurl-thread.3 b/docs/libcurl/libcurl-thread.3 index 745ce474e..b16caa2e8 100644 --- a/docs/libcurl/libcurl-thread.3 +++ b/docs/libcurl/libcurl-thread.3 @@ -101,9 +101,14 @@ are Linux, Solaris and Windows. \fBcurl_global_* functions.\fP These functions are not thread safe. If you are using libcurl with multiple threads it is especially important that before use -you call \fIcurl_global_init(3)\fP to explicitly initialize the library and its -dependents, rather than rely on the "lazy" fail-safe initialization that takes -place the first time \fIcurl_easy_init(3)\fP is called. For an in-depth -explanation refer to \fIlibcurl(3)\fP section \fBGLOBAL CONSTANTS\fP. +you call \fIcurl_global_init(3)\fP or \fIcurl_global_init_mem(3)\fP to +explicitly initialize the library and its dependents, rather than rely on the +"lazy" fail-safe initialization that takes place the first time +\fIcurl_easy_init(3)\fP is called. For an in-depth explanation refer to +\fIlibcurl(3)\fP section \fBGLOBAL CONSTANTS\fP. + +\fBMemory functions.\fP These functions, provided either by your operating +system or your own replacements, must be thread safe. You can use +\fIcurl_global_init_mem(3)\fP to set your own replacement memory functions. \fICURLOPT_DNS_USE_GLOBAL_CACHE(3)\fP is not thread-safe. -- cgit v1.2.3