Просмтор этого файла доступен только зарегистрированным пользователям. Но у нас супер быстрая регистрация: достаточно только электронной почты!

Текст из файла (страница 6)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

EL: <loop number>

Trace body is absent, when trace accumulation is disabled for whole program. Otherwise trace body consists of a lot of records of the following types:

• Reading variable.

RD: [<variable type>] <variable name> = <value>; {<file name>, <line number>}

• Referring to variable (before expression computation)

BW: [<variable type>] <variable name>; {<file name>, <line number>}

• Result of assigning value to variable.

AW: [<variable type>] <variable name> = <value>; {<file name>, <line number>}

• Reading reduction variable. A record in trace file is the following:

RV_RD: [<variable type>] <variable name> = <value>; {<file name>, <line number>}

• Referring to reduction variable (before expression computation)

RV_BW: [<variable type>] <variable name>; {<file name>, <line number>}

• Result of assigning value to reduction variable.

RV_AW: [<variable type>] <variable name> = <value>; {<file name>, <line number>}

• Result of reduction computation:

RV: [<variable type>] <value>; {<file name>, <line number>}

• Skipping a group of statements when referring an element of distributed array in a sequential branch of the program.

SKP: {<file name>, <line number>}

• Parallel loop beginning.

PL: <loop number> (<parent loop number>) [<loop rank>] = <trace level: FULL, MODIFY, NONE>, (<traced iteration range (can be absent)>); {<file name>, <line number>}

• Sequential loop beginning.

SL: <loop number> (<parent loop number>) [<loop rank>] = <trace level: FULL, MODIFY, NONE>, (<traced iteration range (can be absent)>); {<file name>, <line number>}

• Iteration beginning (putted in trace file only when the most nested iteration is executed).

IT: <absolute iteration index (calculated from all values of all iteration variables)>, (<iteration variable value>,<iteration variable value>,…).

• End of parallel loop execution.

EL: <loop number>; {<file name>, <line number>}

15Error messages of Run-Time Library.

The error messages, occurring in process of Run-Time Library operating, can be divided (by error level) on warnings and error messages, breaking the program execution.

The errors, breaking the program execution, can be usual (a user errors most likely) and fatal, requiring, possibly, a participation of program builder.

The error messages have one of the following forms:

*** RTL warning <number of error class> . <error number in class>:
<error message text> ,

*** RTL err <number of error class> . <error number in class>:
<error message text> ,

*** 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. Input/output processor outputs such error messages. 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 with name 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 ordered by class numbers and error numbers in the class are described in document "DVM-program Run-Time system. Detailed design".

16Structure 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 6 and 11.4).

Structure of accumulated trace information is defined by trace mode. In brief mode the following is outputted:

• 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.

When tracing accumulated information also contains all informational messages and messages about Lib-DVM errors.

To make representation of function calls belonging to different nested levels clear, desirable indentation may be specified in parameters, controlling system trace (see section 11.4).

Характеристики

Список файлов учебной работы