If an error occurs in the application ExceptHandler notifies the user and writes error description in log-file. In contradistinction to well-known message Access violation in ... at ... ExceptHandler executes the full error localization. User can also define his own exception class filters on which ExceptHandler will be react. Supported features version 1.3:catching and logging unhandled exceptions;error message includes basic information:exception date and time; exception source class and direct ancestor class;user-defined message; additional information:module and file name; function name and source line number if an error occurred in the user code; sequence of calls that leaded to exception - procedure's stack list; unlimited number of filters based on exception classes for fixing only the desired types of error's in log-file;unique or user-defined log-file name; text-file format is used for logging; switching on standard exception's handler and back; the pop-up window shows and enables:the last exception information with procedure's stack list;moving through the history of appearing the exceptions during the application's executing;user and computer name, Windows version; map-file processing executes in two different ways:direct parsing (slow mode);parsing resource map-file (quick mode, can be used in software distribution but doesn't allow to look through it's contents);for resmap-file security the ExceptHandler component supports the encryption protocol RC6 of RSA Data Security company; for data integrity the cyclical redundancy check CRC32 is used;sends error message for the context debugger;extended analogs of Assert procedure and Win32Check for checking the executing Win32 API functions.
| 
