background image
<< Viewing the Playback Results | Starting Trap >>
<< Viewing the Playback Results | Starting Trap >>

Setting the Trap Options to Detect GPFs

Setting GUI Playback Options
9-17
Setting the Trap Options to Detect GPFs
Robot uses the Trap utility to detect the occurrence of General Protection Faults
(GPF) and the location of offending function calls during playback. If a GPF is
detected, Robot updates a log file that provides information about the state of the
Windows session that was running.
Important Notes
To use the Trap utility, you must include Common Object File Format
(COFF) information in your application when you link. For instructions, see
the documentation for your development environment.
Trap, Visual C++, and Dr. Watson (from Microsoft), WinSpector (from
Borland), and Crash Analyzer (from Symantec) use the same Windows system
calls to trap faults. You cannot use more than one error trapping program at the
same time.
Uses for Trap
The occurrence of a GPF usually results in a crash of the running application and
may also result in a loss of data. Using Trap, you can:
Capture information about GPFs.
Write the state of your environment to a log file when a GPF is detected.
Specify the type of information to write to the log file.
Automatically restart Windows or call your own error handling subprocedure
before performing any other action.
Save an audit of the function where the fault occurred in the failing program.
The Trap utility detects and traps the following events during playback:
UAE: General Protection Fault #13
Stack Overflow: Fault #12
Invalid Op Code: Fault #6
Divide by Zero: Fault #0
If one of these errors occurs, Trap appends the error data to the existing Sqatrap.log
file in the Rational installation directory or creates a new file if one does not exist.
(For more information, see Analyzing Results in the Sqatrap.log File on page 9-18.)