Caution: Do not #include the header file vv_errf.h if you want to use the VCS error reporting system. This header file disables the error reporting system and enables use of your own error handler function.
By default, when using the development libraries and an error is detected, the VCS error reporting system is invoked.
The call log, call stack, error, and, if appropriate, core dump are displayed in windows that appear on the screen when an error is encountered. The screen you see when an error occurs looks like the one in Figure 50.1. If there is not a memory corruption error, the Dump Window is not displayed.
A help window telling you the keys you can use is displayed on the bottom row of the screen. After reviewing the information, hit the key to exit (KEY_ESC for PCDOS) to remove the error reporting windows from the screen. A prompt will appear asking if you want to abort the program or attempt to continue running the program.
If you do not abort the program, you will be asked if you want the system to mask the error. If you specify 'No' then VV_ERR is not reset, allowing you to check your own error recovery code. Note that continuing means you will see the error window many times.
Warning: Most errors reported by the VCS error reporting system are fatal to the program. Continuing the program has unpredictable results.
Figure 50.1: Windows Displayed by the VCS Error Reporting System
Interpreting the Call Log and Call Stack
Interpreting the Contents of the Dump Window
Checking of Call Log and Call Stack Integrity
Controlling the Size of the Call Log and Call Stack
Increasing the Compiler Default Stack Size
