Please enable JavaScript to view this site.

Memory Validator Help

Navigation: Examples > The example application

Building the example application

Scroll Prev Top Next More


Where to find the example application


The example project is in the nativeExample subdirectory where Memory Validator installation directory.


If the directory is not present, reinstall your software and choose custom or full installation to include the examples.



Solutions and projects


There are a variety of solutions and projects for different versions:


nativeExample.dsp instructionStep for Microsoft® Developer Studio® 6.0  

nativeExample_VSx_x.sln instructionStep for Microsoft® Visual Studio / .net




There are a number of configurations in each project, the first two of which are linked with Memory Validator for API use:


Debug / Release instructionStep linked to the svlMemoryValidatorStubLib(_x64).lib demonstrating use with the Memory Validator API  

The other configurations are standalone programs:


DebugNonLink / ReleaseNonLink instructionStep not linked for API use

DebugStatic / ReleaseStatic instructionStep statically linked to the C runtime and not linked for API use

ESA Debug / ESA Release instructionStep uses the Cherrystone Extremely Scalable Allocator (ESA)


You'll need the full or evaluation version of ESA from Cherrystone Software Labs Inc. for these configurations to work.


Using Visual Studio Express?


You might find you can't build the example application with Express versions of Visual Studio because it doesn't provide all the necessary libraries.

If that's the case, try searching for the missing libraries in one of the freely available Windows SDKsexternalLink from the Microsoft website.


note If you use Visual Studio Express to build your own application, Memory Validator will still work with it just fine.



Other projects


There are some other projects installed alongside the nativeExample directory.


These optional projects build various DLLs that can be used by the example program, subject to user interaction.


They demonstrate detection of the loading and unloading of DLLs, memory leaks caused in DLLs that are subsequently unloaded, and other testable behaviours.