Proceedings of the SIGMETRICS Symposium on Parallel and Distributed Tools - SPDT '96 1996
DOI: 10.1145/238020.238030
|View full text |Cite
|
Sign up to set email alerts
|

Event and state-based debugging in TAU

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

1997
1997
2010
2010

Publication Types

Select...
4
2
1

Relationship

0
7

Authors

Journals

citations
Cited by 13 publications
(3 citation statements)
references
References 7 publications
0
3
0
Order By: Relevance
“…The idea of using patterns to assist debug, has been previously proposed in [8] and [9] for debugging parallel programs and have been used for SystemC debugging in [10]. We have used the debug pattern concept to introduce a new language that is suitable for specification of debug patterns for communications.…”
Section: Related Workmentioning
confidence: 99%
“…The idea of using patterns to assist debug, has been previously proposed in [8] and [9] for debugging parallel programs and have been used for SystemC debugging in [10]. We have used the debug pattern concept to introduce a new language that is suitable for specification of debug patterns for communications.…”
Section: Related Workmentioning
confidence: 99%
“…Again, T provides a good example of this feature because tools i i can evoke integrated behavior via synchronized, communicated actions (Brown et al, 1994). Often, the need for interoperability also necessitates extension of the archi-z tecture infrastructure, as in the case of T's program and interaction control infrastructure (Shende et al, 1996).…”
Section: Technology For Domain-specific Environmentsmentioning
confidence: 99%
“…The approach closest to our ideas is that of pattern-oriented parallel debugging pioneered by the program analysis tool Belvedere [5]. This approach was included and extended by the post-mortem event-based debugger Ariadne [2], and later applied in the TAU program analysis environment [11]. Ariadne matches user-specified models of intended program behavior against actual program behavior captured in event traces.…”
Section: Introductionmentioning
confidence: 99%