Please enable JavaScript to view this site.

Memory Validator Help

 

The DLL menu

 

The DLL menu demonstrates the capability of Memory Validator to detect dynamic loading and unloading of DLLs via one of the following Win32 calls:

 

LoadLibrary()

LoadLibraryEx()

FreeLibrary()

 

 

example-dll

 

 

DLL1, DLL2, DLL4, and MFC DLL

 

These four DLLs can each be loaded and unloaded and each has a test function in it, for example:

 

menu DLL1 submenu instructionStep ...

 

Load DLL instructionStep load the DLL
 

Unload DLL instructionStep unload the DLL
 

Test DLL instructionStep call the supplied test function in the DLL

 

The test function performs some memory allocation functions, which may result in memory leaks.

 

See the CTeststakView class methods: OnDllLoaddll1(), OnDllUnloaddll1(), OnDllTestdll1(), etc

 

 

Dependent DLLS

 

The next three options load and unload DLLs having dependent DLLs which should also be loaded:

 

Load Dependent DLLs (using LoadLibrary) instructionStep loads dllADependentOnB.dll
 

This is dependent on dllBDependentOnC.dll which, in turn, is dependent on dllC.dll
 

Load Dependent DLLs (using LoadLibrary via GetProcAddress) instructionStep Similar to the above, but different methods
 

Unload Dependent DLLs instructionStep frees the library if loaded

 
See the CTeststakView class methods: OnDllLoaddependentdlls(), OnDllLoaddependentdlls_LLGPA() and OnDllUnloaddependentdlls().