Starting options
There are four ways to start a target program and have Coverage Validator collect data from it.
•Launch your program in a specified directory, with as many command line arguments as you want
•Inject Coverage Validator into an already running program
•Wait until a specific program starts to run before attaching to it - e.g. for programs started as an OLE server
•Link a library (provided) to your program which will cause Coverage Validator to be started whenever the program is started
There are seven ways to start a target program and have Coverage Validator collect data from it.
•Launch your program in a specified directory, with as many command line arguments as you want
•Inject Coverage Validator into an already running program
•Wait until a specific program starts to run before attaching to it - e.g. for programs started as an OLE server
•Use the Native API to start Coverage Validator from code that you control
•Start Coverage Validator from the command line, allowing you to automate your use of Coverage Validator
Modules without PDB files and without MAP files
For your application to be processed for coverage data, each module to be monitored must have a PDB file with debug data, or a MAP file with line number data.
Use the Debug DLLs dialog to see whether debug information was not found for any modules, and check the Diagnostics tab for failure messages.
