1999
DOI: 10.1007/3-540-48311-x_8
|View full text |Cite
|
Sign up to set email alerts
|

Systematic Debugging of Parallel Programs in DIWIDE Based on Collective Breakpoints and Macrosteps1

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
11
0

Year Published

2001
2001
2021
2021

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 6 publications
(11 citation statements)
references
References 3 publications
0
11
0
Order By: Relevance
“…One feasible way to prove the cloud platform agnostic feature of complex deployment and maintenance strategies is to leverage on advanced systematic debugging/troubleshooting methods in order to find the timing or architecture dependent failures in the designed deployment description and orchestrator. For this purpose, our research team applied and extended the macrostep-based debugging [4] methodology that has been introduced originally for message-passing parallel programs and developed in the P-GRADE graphical programming environment [5].…”
Section: Solutionmentioning
confidence: 99%
See 1 more Smart Citation
“…One feasible way to prove the cloud platform agnostic feature of complex deployment and maintenance strategies is to leverage on advanced systematic debugging/troubleshooting methods in order to find the timing or architecture dependent failures in the designed deployment description and orchestrator. For this purpose, our research team applied and extended the macrostep-based debugging [4] methodology that has been introduced originally for message-passing parallel programs and developed in the P-GRADE graphical programming environment [5].…”
Section: Solutionmentioning
confidence: 99%
“…Early debugging methods in parallel systems relied on the so-called "monitor & replay" approach [4]. In the first monitoring (or recording) phase, the monitoring tool collects as much data about the parallel program as required to reproduce the run in a deterministic way in the second replay phase.…”
Section: Original Concept For Message-passing Programsmentioning
confidence: 99%
“…In the debugging mode, the execution of the program is under the control of the DIWIDE [11] distributed debugger which provides options to create breakpoints, perform step-by-step execution, animation of the flow of control, etc. Once the program has been successfully debugged, it can be executed in trace mode.…”
Section: Tools In P-gradementioning
confidence: 99%
“…Accordingly, systematic testing and debugging of a metacomputing program require (i) generation of its execution tree (ii) exhaustive traverse of its execution tree. With the help of the extended macrostep-by-macrostep concept both of these issues can be solved and implemented in a very similar way as they have been implemented in DIWIDE [8] [12]. Some minor changes are required by the wildcard send operations as well as the event tracing and replaying.…”
Section: Systematic Debugging In Harnessmentioning
confidence: 99%
“…As we studied the related work (such as DejaVu [I], DJVM [ll], DIWIDE [8] [12] integrated in P-GRADE [lo], Macrostep-by-macrostep concept [7], Totalview, P2D2 [4]) we realized that there is a lack of an integrated graphical systematic debugger for metacomputing applications equipped by visualization techniques. Even the most relevant gridlmetacomputing projects such as Globus [3], Condor [13] and Legion [6] do not give efficient solution to the emerging debugging issues.…”
Section: Conclusion and Related Workmentioning
confidence: 99%