Time, clocks, and the ordering of events in a distributed system
Communications of the ACM
A relational approach to monitoring complex systems
ACM Transactions on Computer Systems (TOCS)
Event-based debugging of object/action programs
PADD '88 Proceedings of the 1988 ACM SIGPLAN and SIGOPS workshop on Parallel and distributed debugging
Abstraction Mechanisms for Event Control in Program Debugging
IEEE Transactions on Software Engineering
Modeling concurrency in parallel debugging
PPOPP '90 Proceedings of the second ACM SIGPLAN symposium on Principles & practice of parallel programming
A bibliography of parallel debuggers, 1990 edition
ACM SIGPLAN Notices
High-level language debugging for concurrent programs
ACM Transactions on Computer Systems (TOCS)
Saving traces for Ada debugging
SIGAda '85 Proceedings of the 1985 annual ACM SIGAda international conference on Ada
Execution monitoring and debugging tool for Ada using relational algebra
SIGAda '85 Proceedings of the 1985 annual ACM SIGAda international conference on Ada
DPM: A Measurement System for Distributed Programs
IEEE Transactions on Computers
General Test Result Checking with Log File Analysis
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
As part of a study of methods and strategies for problem solving in a distributed environment [Less80], we have been investigating techniques suitable for use in debugging programs written for implementation on distributed processing networks. Traditional debugging methods emphasize techniques that apply at the level of computation units and generally allow users to examine, and possibly alter, the state of a computation. Interactive debugging monitors are probably the most powerful implementations of the traditional method and usually permit a user to examine an entire snspshot of system state at any step of the computation. It is the job of the debugger (usually a person directing the error search) to determine what units are relevant to some problem, examine the units in whatever fashion is available, and then fit the results of these examinations into a model of how the computation works. Two elements essential to the successful completion of the debugging task are evident here: the ability to monitor, in some meaningful way, the relevant system activity so as to understand how system behavior differs from the debugger's model, and the ability to perform experiments based (implicitly or explicitly) on the information gathered. Through the interaction of these two elements a debugger attempts to gain an understanding of the causes of an error or at least to note where the implementation and the expected behavior differ.