Документ взят из кэша поисковой машины. Адрес оригинального документа : http://sp.cs.msu.ru/dvm/dvmhtm1107/eng/sys/debug/debugDDe4.html
Дата изменения: Mon Feb 13 12:59:06 2006
Дата индексирования: Mon Oct 1 23:25:49 2012
Кодировка:
DVM debugger. Detailed design. Part 4
DVM debugger - contents Part 1 (1 - 4) Part 2 (5 - 6.4) Part 3 (6.5) Part 4 (7)
document data: March 2000 - last edited 22.05.01 -

7 Diagnostic messages of the dynamic debugger

Table 1. The messages of dynamic control of DVM-directives

Error message

Description

Writing to read-only variable <var> Writing to read-only variable is detected.
Using non-initialized variable <var> Access to non-initialized variable is detected.
Using non-initialized element <elem> Access to non-initialized array element is detected.
Using variable <var> before asynchronous reduction competed Access to reduction variable before reduction operation completion is detected.
Access to non-local element <elem> Access to non-local element of distributed array is detected.
Writing to shadow element <elem> of array Writing to shadow element of array is detected.
Data dependence in loop due to access to element <elem> Data dependence in parallel loop is detected.
Using shadow element <elem> before asynchronous shadow renew competed The dynamic debugger detects access to a shadow element before asynchronous shadow renew competed
Writing to remote data buffer <var> Writing to remote data buffer is detected.
Write to remote element <elem> in sequential branch Access to array element in sequential branch of program without preliminary testing that the element is located on current processor.
Reading remote element %s in sequential branch Access to non-local array element in sequential branch of program is detected.
WAIT for reduction without START Waiting for asynchronous reduction completion is issued without Start asynchronous reduction.
Using element outside of array limits: <elem> Access to element of array beyond its limits.
START for reduction without WAIT The wait operation is missing for started asynchronous reduction calculation.
Reduction operation was not started The reduction variable is specified but the reduction calculation is never performed.

Table 2. The messages of comparing execution results

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 program construct) It is reported, if iteration or task beginning or structure completion event occurs without correspondent structure beginning event.
No current program construct It is reported if iteration or task beginning or structure completion event occurs without corresponding structure beginning event.
Unexpected task or iteration of loop It is reported if iteration or task beginning event occurred, but there is no correspondent record in reference trace.
Double execution of task or iteration, No = <iteration number> It is reported if iteration or task beginning event occurs for already executed loop iteration or task. Absolute iteration number is reported.
Unexpected execution of program construct It is reported if structure 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 if there is no record in reference trace for variable access event.
Unexpected trace record It is reported if there is no record in reference trace for an event of completion of self-calculation block 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.

DVM debugger - contents Part 1 (1 - 4) Part 2 (5 - 6.4) Part 3 (6.5) Part 4 (7)