DEB_GUID (1158345), страница 6
Текст из файла (страница 6)
*** RTL fatal err <number of error class> . <error number in class>:
<error message text> ,
The error class is defined by functional and module structure of Run-Time Library.
The file name and line number (as user program, as Run-Time Library), where the error occurred are reported before the error message:
USRFILE=<file name of user program>; USRLINE=<line number>;
SYSFILE=<file name of Run-Time Library>; SYSLINE=<line number>;
The errors may be divided on two groups according to their occurrence way. The first group is the errors, occurring on all the processors at once. Such error messages are output by input/output processor. The second group is the errors that can occur not on all the processors. Each processor outputs such error messages itself, adding to the message its internal and external numbers. When working on one processor, the error messages are output without its numbers.
Run-Time Library provides possibility to output all error messages of the first group by all the processors and all errors of the second group only by input/output processor. The first possibility is implemented if the parameter MultiProcErrReg is set equal to 2 (parameter files syspar.*). To output error messages of the second group only by input/output processor this parameter must be equal to zero (this possibility is used only in experimental purposes). Standard value of parameter MultiProcErrReg is equal to 1.
The error messages, divided by subjects and ordering by class numbers and error numbers in the class are described in document "LIB-DVM library. Detailed design".
16.Structure of system trace file.
The system trace file has the following structure:
The event of function call has the name call_<function_name>.
The event of return from function has the name ret_<function_name>.
The trace of each event cab be enabled or disabled by its number (see section Error: Reference source not found).
Structure of accumulated trace information is defined by trace mode. In brief mode the following is outputed:
-
event name;
-
time, passed from previous event;
-
name of user program file and line number in the file, defining event point in the program.
In detailed trace mode saving information is extended and depends on event type. If the event is function call, then its call parameters are outputted. When returning function its result parameters are output. For each event the detailed trace mode can be specified independently of common mode.
To make representation of function calls belonging to different nested levels clear, desirable indentation may be specified in parameters, controlling system trace (see section Error: Reference source not found).
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
