Avoid Re-initialization of Critical Section

Question

Exact Duplicate

Initialize Critical Section only once for a process

I have a dll that creates a global critical section, initializes and use it.

Now a third party application is using / loading the dll more than once which leads to a heap corruption.

The appverifier warns me with a

--> VERIFIER STOP 00000211: pid 0x1470: Critical section is already initialized. <--

Using a global flag to check if the critical section object is already initialized doesn't help, any ideas on accomplishing the same ?

Thanks

Answer 1

Have you looked at this question for a possible answer?

http://stackoverflow.com/questions/724560/initialize-critical-section-only-once-for-a-process

Answer 2

Now a third party application is using / loading the dll more than once

Windows does not reload the same DLL multiple times. Where same means same path. If the 3rd party app is loading from different locations, that is the problem.

Answer 3

May be using the "setAtom" and "getAtom" APIs help? I know they are a bit "old-school" but you can never know.