From 19ca40100bf5ca5ee8511b193bdb1f8e95152664 Mon Sep 17 00:00:00 2001 From: Jay Satiro Date: Mon, 4 Jan 2016 17:44:39 -0500 Subject: curl_global_init.3: Add Windows-specific info for init via DLL - Add to both curl_global_init.3 and libcurl.3 the caveat for Windows that initializing libcurl via a DLL's DllMain or static initializer could cause a deadlock. Bug: https://github.com/bagder/curl/issues/586 Reported-by: marc-groundctl@users.noreply.github.com --- docs/libcurl/curl_global_init.3 | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'docs/libcurl/curl_global_init.3') diff --git a/docs/libcurl/curl_global_init.3 b/docs/libcurl/curl_global_init.3 index 77172be67..2e489c1a8 100644 --- a/docs/libcurl/curl_global_init.3 +++ b/docs/libcurl/curl_global_init.3 @@ -50,6 +50,10 @@ This doesn't just mean no other thread that is using libcurl. Because similarly thread unsafe, it could conflict with any other thread that uses these other libraries. +If you are initializing libcurl from a Windows DLL you should not initialize it +from DllMain or a static initializer because Windows holds the loader lock +during that time and it could cause a deadlock. + See the description in \fBlibcurl(3)\fP of global environment requirements for details of how to use this function. -- cgit v1.2.3