How to loadlibrary from a new thread

Hello everyone,

I've searched the forum for an answer to my newbie question, but found nothing directly related to it...although lots of good stuff about DLL's.

In my little program in the main() I successfully use LoadLibrary and GetProcAddress and call a couple of functions in a DLL. In short, the DLL works as such. Then, I CreateThread(...) and create a new thread. The function called by CreateThread attempts to do a LoadLibrary and GetProcAddress to the SAME DLL. Nothing happens. No error messages, no nothing. The function invoked by CreateThread gets to the line in which LoadLibrary is called and does nothing. Program exits without errors.

The DLL itself has a BOOL WINAPI DllMain entry point with the "usual" DLL_PROCESS_ATTACH, etc. values in a switch block.

It seems like what I'm trying to do should work, but it doesn't. I have zero tech support, and I'm out of ideas.

Thanks for considering this problem.

Regards to all,
Mark Allyn

Have you tried passing the address of the DLL that you got from the first LoadLibrary into the function that is being run by the new thread?

DLLs are loaded into the address space of the entire process so you don't really need to call LoadLibrary again unless the main thread might unload the library before the second thread is done with it.

Are you sure that the functions you're calling aren't working properly? Is there a reason that the program should stay open for longer than that?

Isn't it a platform specific thread?

Moved to Windows Programming.

What does GetLastError() return?

Generally DDLs loaded at runtime (dynamically) should either;

have global scope (loaded once and passed around as required)

or

loaded, used and released as required.

This depends on the requirements of the app and the DLL.

Also IIRC once a process has called LoadLibrary() on a particular DLL (and so 'mapped' it) the DLLMain() will not get called again by the same process (until the DLL is unmapped with a call to FreeLibrary() ).