DEB_DD (1158343), страница 10
Текст из файла (страница 10)
2 – join of the two previous modes.
3 – compare the execution result trace with the standard trace file TraceOptions.TraceFile.
-
TraceOptions.TraceLevel – trace level.
0 – disable tracing.
1 – trace loops and iterations only.
2 – the previous level plus trace variable modifications.
3 – trace all loops, iterations and variable accesses.
-
TraceOptions.SpaceIndent – the indent size that is used in the trace files.
-
TraceOptions.ErrorToScreen – if this parameter is not equal to 0 then all diagnostic messages will be output to the screen.
-
TraceOptions.TableTraceSize – increment size of the trace table
-
TraceOptions.HashIterIndex and TraceOptions.HashIterSize – hash-table parameters.
-
TraceOptions.ReductHashIndexSize, TraceOptions.ReductHashTableSize and TraceOptions.ReductVarTableSize – the parameters of the reduction variable-table.
-
TraceOptions.SaveThroughExec – the trace will be written into the file during program execution if this parameter is not equal to 1. Otherwise the trace will be accumulated in the memory and written after program completion. You can enable this mode only if the loop description file is exist.
-
TraceOptions.PrintStatistic – flag to enable or disable output of the trace statistics.
-
TraceOptions.WriteEmptyIter – if it is equal to 0 then the empty iterations are not put into the trace.
-
TraceOptions.AppendErrorFile – the mode of a diagnostic file usage. The file will be cleared each time before program startup if the parameter is equal to 0.
-
TraceOptions.MaxErrors – the maximum count of errors after that the trace accumulation or comparing is disabled.
4.6.Error messages
The common error message structure of execution result tracing module is the following:
(<process number>)<context> File: <file>, Line: <line>
(<count> times)<error message>
where
<process number> – processor number where the error occurs. The processor number is printed only in the case of running the program on a several processors.
<context> – context description where the error occurs. It can be one of the following forms:
Sequential branch – the error occurs in the sequential branch of the program.
Loop( No(N1), Iter(I1,I2,…) ), …, Loop( No(Nm), Iter(I1,I2,…) ) – the error occurs during performance of a m-dimensional loop nest.
<file> – the file name where the error occurs.
<line> – the line number where the error occurs.
<count> – number of repetitions of this error in the context. It is printed only when a summary information about all detected errors is printed.
<error message> – error description message. The list of all possible messages is showed in the following table:
| Error message | Description |
| Bad file structure | It is reported when any non-correspondence of trace or loop description file is detected. |
| Undefined keyword | It is reported if unknown keyword appears in trace or loop description file. |
| Bad command syntax | It is reported, if wrong parameters appear after keyword. |
| Can't open a file <file name> | Specified file can’t be open on reading or writing. |
| Trace file is empty | Specified trace file exists, but it is empty. |
| Bad trace structure (missing current loop) | It is reported, if iteration beginning or loop end event occurs without correspondent loop starting event. |
| No current loop | It is reported if iteration beginning or loop end event occurs without corresponding loop beginning event. |
| Unexpected iteration of loop | It is reported if iteration beginning event occurred, but there is no correspondent record in reference trace. |
| Double execution of iteration, No = <iter no> | It is reported if iteration beginning event occurs for executing loop iteration. Absolute iteration number is reported. |
| Unexpected loop execution | It is reported if loop beginning event occurs, but there is no correspondent record in reference trace. |
| Abnormal loop exit | It is reported if record of loop end is not corresponds to the record of loop beginning. |
| Unexpected use of variable | It is reported there is no record in reference trace for variable access event. |
| Unexpected trace record | It is reported there is no record in reference trace for an event of possible skip of group operators in the sequential branch. |
| Different <type> values: <standard value> != <current value> | Different values of the same variable are detected for current event and in reference trace record. |
| Different <type> values of reduction variable: <standard value> != <current value> | Different values of reduction operation are detected for current event and in reference trace record. |
![](https://s.studizba.com/z.php?f=/templates/si/i/noavatar.png&w=100&h=100&t=1"){kind=avatar}
