Thread and dll question

I have a small program that uses threads - if i load in a dll with functions that the threads will use, will a dll be loaded in for each thread or will only one dll be loaded and the threads share access to it?  Also, if two or more threads need to access the dll, should i ensure the dll is thread safe or is each thread able to access the dll as if the thread was a different program?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Russell LibbySoftware Engineer, Advisory Commented:
Regarding your questions....

1.) A dll is loaded only once per process, not per thread. Additional "loads" only increment the ref count on the dll. (You can code the DLLMain entry point to test this, eg)

library Project1;


procedure DLLMain(Reason: Integer);

  // Handle calling based on reason code
  case Reason of
     DLL_PROCESS_DETACH   :  ; // Check count of detatch
     DLL_PROCESS_ATTACH   :  ; // Check count of attach
     DLL_THREAD_ATTACH    :  ;
     DLL_THREAD_DETACH    :  ;



  // Change the dll proc

  // Need to call it with process attach


2.) All process threads will share the dll. If you need to do something specific (like thread local storage, etc), then the DLLmain entry point is a good place for it.

3.) If you want the dll to be thread safe, then you will need to code it as such. Eg, through the use of crtical section/mutex/etc access to shared resources.


Hope this helps,


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Russell is completely right, of course. Just some little extensions:

Local variables are always thread safe. Your dll is automatically thread safe if you're not using any global resources/variables. As soon as multiple threads have (or can potentially have) access to the same variable/resource at the same time, you need to synchronize access to it - using one of the methods Russell mentioned in 3.).
or use a threadvar - each thread gets it's own copy of the global var :)
but I prefer a proper sync over threadvars anytime
Russell LibbySoftware Engineer, Advisory Commented:

Question was answered by all three participants.

By the way...
"thanks" for the work you do, it truly is appreciated.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.