Loads the profiler DLL into memory, but does not start the profiler.
Use this for:
32 bit applications with a 32 bit Coverage Validator GUI
64 bit applications with a 64 bit Coverage 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 Coverage Validator, or when you injected into your program using Inject or Wait For Application.
However if you're running your program from outside of Coverage Validator and want to load the profiler from inside your program you can use cvLoadProfiler() to do that. You'll then need to call cvStartProfiler() or cvStartProfilerWithOwnGUI() to start it.
extern "C"
int cvLoadProfiler();
Returns:
TRUE Successfully loaded PV DLL into target application.
FALSE Failed to load the PV DLL.into target application.
Check that the PATH environment variable points to the Coverage Validator install directory contains svlCoverageValidatorStub*.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 Coverage 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 Coverage Validator, or when you injected into your program using Inject or Wait For Application.
However if you're running your program from outside of Coverage Validator and want to load the profiler from inside your program you can use cvLoadProfiler6432() to do that. You'll then need to call cvStartProfiler() or cvStartProfilerWithOwnGUI() to start it.
extern "C"
int cvLoadProfiler6432();
Returns:
TRUE Successfully loaded PV DLL into target application.
FALSE Failed to load the PV DLL.into target application.
Check that the PATH environment variable points to the Coverage Validator install directory contains svlCoverageValidatorStub*.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 cvStartProfiler() from your code before you call any API functions. Ideally you should call this function as early in your program as possible.
This will look for an existing Coverage Validator user interface and send profiling results to that. If no Coverage Validator user interface is running, cvStartProfiler() will start a new Coverage Validator user interface.
extern "C"
int cvStartProfiler();
Returns:
TRUE Successfully started PV profiler.
FALSE Failed to start the PV profiler.
If you prefer to start the profiler from the user interface or command line you can omit the cvStartProfiler() call. You can leave it present if you wish to start Coverage Validator from your program.
Do not use this function if you are working with services, use the NT Service API.
This function is the same as cvStartProfiler() except that this always starts a new Coverage Validator user interface to receive the profiling results.
Use this function if you want to profile multiple processes at the same time (one Coverage Validator user interface per process being profiled).
extern "C"
int cvStartProfilerWithOwnGUI();
Returns:
TRUE Successfully started CV profiler.
FALSE Failed to start the CV profiler.
If you prefer to start the profiler from the user interface or command line you can omit the cvStartProfilerWithOwnGUI() call. You can leave it present if you wish to start Coverage Validator from your program.
Do not use this function if you are working with services, use the NT Service API.
This function is how you start the profiler from the API if you are using the -waitForAPI command line option.
Use this function if you want to use Coverage Validator from the command line and have it wait for an application connect to it via the API.
extern "C"
int cvStartProfilerWaitForAPI(const int insistOnNoSessions,
const DWORD waitTimeout,
const int launchNewGUIIfTimeoutExpired);
The API will search for Coverage Validator instances that meet the insistOnNoSessions criteria for a maximum of waitTimeout seconds.
If the timeout expires and launchNewGUIIfTimeoutExpired is TRUE a new Coverage Validator instance is launched, otherwise attaching to Coverage Validator fails.
If insistOnNoSessions is FALSE any Coverage Validator that is found that is in the Ready state will be connected with.
If insistOnNoSessions is TRUE any Coverage Validator that is found that is in the Ready state will be connected with if it does not have any recorded sessions.
Returns:
TRUE Successfully started CV profiler.
FALSE Failed to start the CV profiler.
Do not use this function if you are working with services, use the NT Service API.