Loads the profiler DLL into memory, but does not start the profiler.
Use this for:
32 bit applications with a 32 bit Memory Validator GUI
64 bit applications with a 64 bit Memory Validator GUI
For most use cases won't need to load the profiler, as the profiler will have been loaded when your launched your program from Memory Validator, or when you injected into your program using Inject or Wait For Application.
However if you're running your program from outside of Memory Validator and want to load the profiler from inside your program you can use mvLoadProfiler() to do that. You'll then need to call mvStartProfiler() to start it.
extern "C"
int mvLoadProfiler();
Returns:
TRUE Successfully loaded MV DLL into target application.
FALSE Failed to load the MV DLL.into target application.
Check that the PATH environment variable points to the Memory Validator install directory contains svlMemoryValidatorStub*.dll.
Do not use this function if you are working with services, use the NT Service API.
Loads the profiler DLL into memory, but does not start the profiler.
Use this for:
32 bit applications with a 64 bit Memory Validator GUI
For most use cases won't need to load the profiler, as the profiler will have been loaded when your launched your program from Memory Validator, or when you injected into your program using Inject or Wait For Application.
However if you're running your program from outside of Memory Validator and want to load the profiler from inside your program you can use mvLoadProfiler6432() to do that. You'll then need to call mvStartProfiler() to start it.
extern "C"
int mvLoadProfiler6432();
Returns:
TRUE Successfully loaded MV DLL into target application.
FALSE Failed to load the MV DLL.into target application.
Check that the PATH environment variable points to the Memory Validator install directory contains svlMemoryValidatorStub*.dll.
Do not use this function if you are working with services, use the NT Service API.
To start the profiler from your API code you need to call the function mvStartProfiler() from your code before you call any API functions. Ideally you should call this function as early in your program as possible.
extern "C"
int mvStartProfiler();
Returns:
TRUE Successfully started MV profiler.
FALSE Failed to start the MV profiler.
If you prefer to start the profiler from the user interface or command line you can omit the mvStartProfiler() call. You can leave it present if you wish to start Memory Validator from your program.
Do not use this function if you are working with services, use the NT Service API.
To test if Memory Validator has loaded into this application call mvIsValidatorPresent().
extern "C"
int mvIsValidatorPresent();
Returns:
TRUE Memory Validator is loaded into this process.
FALSE Memory Validator is not loaded into this process.