EUROMICRO 97. Proceedings of the 23rd EUROMICRO Conference: New Frontiers of Information Technology (Cat. No.97TB100167)
DOI: 10.1109/eurmic.1997.617289
|View full text |Cite
|
Sign up to set email alerts
|

An integrated testing and debugging environment for parallel and distributed programs

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
4
0
2

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 13 publications
(6 citation statements)
references
References 4 publications
0
4
0
2
Order By: Relevance
“…Among the diversity of parallel software development tools, one can find tools focusing on performance evaluating and tuning [4,15,18,24,25], and other focusing on program correction aspects [4,14,28,30]. One can also find tools providing distinct operation modes: i) Tools which may operate on-line with a running distributed application in order to provide an interactive user interface [4,11,14,30]; ii) Tools which can be used to enforce a specific behavior upon the distributed application by controlling its execution, e.g., as described in some kind of script file [22,26,27]; iii) Tools which may deal with the information collected by a tracing tool as described in a log file [4,15,16,18,25].…”
Section: Multiple Distributed Debugging Methodologiesmentioning
confidence: 99%
See 1 more Smart Citation
“…Among the diversity of parallel software development tools, one can find tools focusing on performance evaluating and tuning [4,15,18,24,25], and other focusing on program correction aspects [4,14,28,30]. One can also find tools providing distinct operation modes: i) Tools which may operate on-line with a running distributed application in order to provide an interactive user interface [4,11,14,30]; ii) Tools which can be used to enforce a specific behavior upon the distributed application by controlling its execution, e.g., as described in some kind of script file [22,26,27]; iii) Tools which may deal with the information collected by a tracing tool as described in a log file [4,15,16,18,25].…”
Section: Multiple Distributed Debugging Methodologiesmentioning
confidence: 99%
“…In order to support reproducible behavior, the distributed debugger should allow the implementation of a trace and replay approach for interactive cyclic debugging. Furthermore, the distributed debugger should provide support for a systematic state exploration of the distributed computation space, even if such a search is semi-automatic and user-driven [22].…”
Section: Multiple Distributed Debugging Methodologiesmentioning
confidence: 99%
“…In order to support systematic debugging of message passing parallel programs and to eliminate the unpredictable effect of single global breakpoints STEPS [13] introduced the concept of global breakpoint sets that was applied in DDBG [4] , [18]. They also introduced the notion of step that means to execute the parallel program until the next global breakpoint set that is generated by the tool STEPS.…”
Section: Collective Breakpointsmentioning
confidence: 99%
“…RecPlay [173], DIOTA [123], JaRec [71], DejaVu [33,103], Optimal Shared-Memory Replay [144], JNuke [184], Flight Data Recorder [231], BugNet [142] e Flashback [196] para sistemas de memória compartilhada, bem como o MAD [104], Optimal Message Replay [148], DPD [189], DEIPA [118], PDT [37], IVD [122], Buster [229] Uma segunda vertente das ferramentas de re-execução, particular dos sistemas de memória compartilhada, são aquelas que operam sob o princípio que a reprodução do comportamento do escalonador é suficiente para garantir uma re-execução correta [33,103,184,196]. O problema com essa hipótese é que ela se sustenta apenas para sistemas pseudo-paralelos.…”
Section: Re-execução Determinística (Replay Debugging)unclassified