doing things when dll's are loaded...

Printable View

12-11-2003
seec77

doing things when dll's are loaded...

i want to do some initializing when a dll is loaded.... this is my dll of course, and what i want to do is actually initialize winsock...
ok...
this is my code for DllMain:

Code:

BOOL APIENTRY DllMain (HINSTANCE hInst /* Library instance handle. */ , DWORD reason /* Reason this function is being called. */ , LPVOID reserved /* Not used. */ ) { switch (reason) { case DLL_PROCESS_ATTACH: break; case DLL_PROCESS_DETACH: break; case DLL_THREAD_ATTACH: break; case DLL_THREAD_DETACH: break; } /* Returns TRUE on success, FALSE on failure */ return TRUE; }

where exactly should i put it? (keep in mind i also want to denitialize and cleanup winsock when the dll is unloaded...)

thanks in advance!
seec77
12-11-2003
Codeplug

Code:

case DLL_PROCESS_ATTACH: WSAStartup(wVersion, &WSAData); break; ... case DLL_PROCESS_DETACH: WSACleanup(); break;

gg
12-11-2003
Nor

you using a dll?
export export export

export some OnLoad() OnExit() functions.
when you load the dll call the OnLoad(). place your initializing code there.
then your ready to go
12-12-2003
seec77

Quote:

Originally posted by Nor
you using a dll?
export export export

export some OnLoad() OnExit() functions.
when you load the dll call the OnLoad(). place your initializing code there.
then your ready to go

i'd rather go with Codeplug's suggestion....
thank you both!!!
:D

p.s.
what is "gg"?!?!
12-12-2003
Codeplug

gg - my initials ;)
12-12-2003
seec77

weird...
it didn't work...
i put the initialization code inside the process_attach, and when i ran the program, it went kaboom
then, when i put the initialization code inside the first function that was called, it worked... and i compiled it in the same way btw!
12-12-2003
seec77

ok... this is really weird....
i just understood that my DllMain function isn't even called! :eek:
first of all i tried putting the winsock initialization code in the body of the function and it still didn't work.... then i commented the whole function out, and it gave me no error!

Code:

BOOL APIENTRY DllMain (HINSTANCE hInst /* Library instance handle. */ , DWORD reason /* Reason this function is being called. */ , LPVOID reserved /* Not used. */ ) { ... }

anything wrong with this code? this is really weird!
thanks in advance!
12-12-2003
anonytmouse

The range of functions that can be called in DllMain is extremely limited.

Quote:

MSDN Documentation for DllMain
Warning The entry-point function should perform only simple initialization or termination tasks. It must not call the LoadLibrary or LoadLibraryEx function (or a function that calls these functions), because this may create dependency loops in the DLL load order. This can result in a DLL being used before the system has executed its initialization code. Similarly, the entry-point function must not call the FreeLibrary function (or a function that calls FreeLibrary), because this can result in a DLL being used after the system has executed its termination code.

I think it is safe to say that WSAStartup calls LoadLibrary or its equivalent.

If you do not provide a DllMain the compiler provides a default version. Try putting a MessageBox in it if you are worried that it is not being called.
12-12-2003
seec77

damn...
then WSAStartup uses LoadLibrary?
damn...
so how can i go about doing this???
btw, i do think DllMain is only called if you use the LoadLibrary function to open it, and not just do a __declspec (dllimport)
and are you sure it's not allowed at all, or is it just not recommended (using LoadLibrary or FreeLibrary in DllMain)
thanks so far!
12-12-2003
anonytmouse

so how can i go about doing this???

As Nor suggested. Use descriptive names like MyLibraryStartup and MyLibraryCleanup.

btw, i do think DllMain is only called if you use the LoadLibrary function to open it, and not just do a __declspec (dllimport)

I think it is always called.

and are you sure it's not allowed at all, or is it just not recommended (using LoadLibrary or FreeLibrary in DllMain)

Your process going kaboom suggests that it is not allowed. Even if you ignore the documentation and get something working it may break on other versions of Windows.
12-12-2003
Codeplug

The code I posted is from source code that's running "in the field" (on NT, 2000, XP, CE 2.11).
However, it's since been changed to not make those calls in DllMain() for other reasons.

You'll know if it works once DllMain() is being called (duh).
What compiler you using? And how are you compiling/linking?

gg
12-12-2003
seec77

first of all....
please excuse me for being so stupid....
secondly, im using dev-cpp, and im compiling... ummm.... normally....
i make the output dll and object files to another directory where my "client" project is... then, the client project uses LoadLibrary and GetProcAddress to call the functions off the dll....