Re: DllMain entrypoint - Is it serialized?
There ain't no such thing as a named critical section. You are probably
thinking of a named mutex.
you are rights.
In that case, I hope your dll is not going to be used on Windows 2000,
because initializing named objects on win2000 can cause the loading
of a dll, which can cause a deadlock. This is documented in msdn.
Can you provide a relevant quote from MSDN? The documentation on DllMain
has this to say:
Documentation on DllMain is inconsistent at best. I first searched my local
MSDN install, but couldn't find that information anymore.
Then I checked the same article on MSDN2, and it contained what I was
refering to, near the bottom of the page.
In MSDN:
http://windowssdk.msdn.microsoft.com/en-us/library/ms682583.aspx
Windows 2000: Do not create a named synchronization object in DllMain
because the system will then load an additional DLL. This restriction does
not apply to subsequent versions of Windows.
And in a best practises document:
From
download.microsoft.com/download/a/f/7/af7777e5-7dcd-4800-8a0a-b18336565f5b/DLL_bestprac.doc
You should never perform the following tasks from within DllMain:
? Create a named pipe or other named object (Windows 2000 only). In
Windows 2000, named objects are provided by the Terminal Services DLL. If
this DLL is not initialized, calls to the DLL can cause the process to
crash.
--
Kind regards,
Bruno van Dooren
bruno_nos_pam_van_dooren@hotmail.com
Remove only "_nos_pam"