We have an application containing many (hundreds) DLLs. The EXE directly depends on part of them (via its Import Table), which in turn depend on another part (via their Import Tables) and so on. Out of all these DLLs there is one, that both the EXE and most of DLLs depend on. This DLL is one of the first to be (statically) loaded at the application startup.

There have been many questions about how to identify the process’ main thread. A common answer was that there is no “main” thread and all threads are equivalent.

There have been many questions about how to identify the process’ main thread. A common answer was that there is no “main” thread and all threads are equivalent.