1. Open the Run Program dialog box.
2. In Collect Data From, select Unmanaged code to monitor a native code program, Managed code to monitor a p-code program or a Visual Basic .NET managed code program.
3. In Program name, click to select the name of the program you want to monitor.
4. In Command-line arguments, enter any arguments required by your program.
5. Specify the working directory to use for the current run.
6. Click Settings to specify settings for this and future runs of the program.
7. Click Run. PureCoverage starts monitoring the program and displays the Run Summary window.
Notes:
§ To stop monitoring a program, select File > Cancel Run or click
§ To rerun a program with the same settings, select File > Run Again or click
§ Line level coverage data is not available when you monitor a Visual Basic p-code program.
§ When you monitor p-code launched by a container program, PureCoverage collects coverage data for any Visual Basic p-code that runs before your p-code is run. If this occurs, use the Run Control toolbar to start and stop recording, and clear data, or use the corresponding PureCoverage API functions, to isolate the data for your p-code.
§ The Visual Basic default compile option is to compile to p-code. To compile to native code instead, select Project > <project name> Properties and, in the Compile tab, select Compile to Native Code. Select also No Optimization and Create Symbolic Debug Info. Then select File > Make <project>.exe. Visual Basic makes the native-code executable file, creates the associated .pdb files, and places them in the program directory.
§ The Microsoft Visual Basic native-code compiler currently does not:
§ Encode any information about a procedure's arguments. Consequently, PureCoverage displays the argument list as (...) in all cases.
§ Retain project and sub-project information about procedures. Consequently, if you have a main project called MyVBProject and a sub-project called VBHello, and it defines a procedure called HiWorld, PureCoverage displays the name as VBHello.HiWorld(...), rather than as MyVBProject.VBHello.HiWorld().
§ PureCoverage uses the debug information in .pdb files to compose the procedure names it displays. In general, procedure and subroutine names in .frm files appear as Module.procedure(...). Procedures in .bas files appear as Procedure(...).
§ Debug symbol data must be available for PureCoverage to identify a procedure. If it is not, PureCoverage labels the procedures UnnamedProcedure@<offset>; for example, UnnamedProcedure@0x124d. For certain procedures, Visual Basic never provides symbol data.
(C) Copyright IBM Corporation 1993, 2010.