WARNING! Gitlab maintenance operation scheduled for Thursday, 18 June between 19:00 and 20:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.

Commit 19ca4010 authored Jan 04, 2016 by Jay Satiro

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>

parent b8235964

docs/libcurl/curl_global_init.3

+4 −0

Original line number	Diff line number	Diff line
		@@ -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.

docs/libcurl/libcurl.3

+3 −0

Original line number	Diff line number	Diff line
		@@ -194,6 +194,9 @@ object as the program starts up and the destructor as it terminates. As the
		author of this libcurl-using module, you can make the constructor call
		\fIcurl_global_init(3)\fP and the destructor call \fIcurl_global_cleanup(3)\fP
		and satisfy libcurl's requirements without your user having to think about it.
		(Caveat: 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.)

		\fIcurl_global_init(3)\fP has an argument that tells what particular parts of
		the global constant environment to set up. In order to successfully use any