关于dllMain死锁的问题

最新推荐文章于 2021-12-24 08:50:35 发布

最新推荐文章于 2021-12-24 08:50:35 发布 · 518 阅读

多线程专栏收录该内容

1 篇文章

订阅专栏

本文通过一次实际遇到的死锁问题，介绍了在DLLMain函数中应避免执行的任务，包括加载库文件、同步线程等操作，并给出了可以在DLLMain中安全执行的任务列表。

前几天遇到了一个死锁问题，查了很久没查出来，最后发现是在dllMain中结束线程导致死锁。

起因：是修改了某个模块，在init函数里启动线程，在uninit函数里结束线程，开始并不知道init和uninit是从dllMain调过来的，也不知道dllmain中结束线程会导致死锁。

具体原因：每次进入dllMain时都会持有一个loader-lock，而结束线程也会进入dllMain，结果就死锁了。

在这里列出msdn的建议，防止再次犯错：

You should never perform the following tasks from within DllMain:

Call LoadLibrary or LoadLibraryEx (either directly or indirectly). This can cause a deadlock or a crash.
Call GetStringTypeA, GetStringTypeEx, or GetStringTypeW (either directly or indirectly). This can cause a deadlock or a crash.
Synchronize with other threads. This can cause a deadlock.
Acquire a synchronization object that is owned by code that is waiting to acquire the loader lock. This can cause a deadlock.
Initialize COM threads by using CoInitializeEx. Under certain conditions, this function can call LoadLibraryEx.
Call the registry functions. These functions are implemented in Advapi32.dll. If Advapi32.dll is not initialized before your DLL, the DLL can access uninitialized memory and cause the process to crash.
Call CreateProcess. Creating a process can load another DLL.
Call ExitThread. Exiting a thread during DLL detach can cause the loader lock to be acquired again, causing a deadlock or a crash.
Call CreateThread. Creating a thread can work if you do not synchronize with other threads, but it is risky.
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.
Use the memory management function from the dynamic C Run-Time (CRT). If the CRT DLL is not initialized, calls to these functions can cause the process to crash.
Call functions in User32.dll or Gdi32.dll. Some functions load another DLL, which may not be initialized.
Use managed code.

The following tasks are safe to perform within DllMain :

Initialize static data structures and members at compile time.
Create and initialize synchronization objects.
Allocate memory and initialize dynamic data structures (avoiding the functions listed above.)
Set up thread local storage (TLS).
Open, read from, and write to files.
Call functions in Kernel32.dll (except the functions that are listed above).
Set global pointers to NULL, putting off the initialization of dynamic members. In Microsoft Windows Vista™, you can use the one-time initialization functions to ensure that a block of code is executed only once in a multithreaded environment.