The Community for Technology Leaders
Green Image
Issue No. 04 - April (1987 vol. 36)
ISSN: 0018-9340
pp: 471-482
T.J. Leblanc , Department of Computer Science, University of Rochester
The debugging cycle is the most common methodology for finding and correcting errors in sequential programs. Cyclic debugging is effective because sequential programs are usually deterministic. Debugging parallel programs is considerably more difficult because successive executions of the same program often do not produce the same results. In this paper we present a general solution for reproducing the execution behavior of parallel programs, termed Instant Replay. During program execution we save the relative order of significant events as they occur, not the data associated with such events. As a result, our approach requires less time and space to save the information needed for program replay than other methods. Our technique is not dependent on any particular form of interprocess communication. It provides for replay of an entire program, rather than individual processes in isolation. No centralized bottlenecks are introduced and there is no need for synchronized clocks or a globally consistent logical time. We describe a prototype implementation of Instant Replay on the BBN Butterfly? Parallel Processor, and discuss how it can be incorporated into the debugging cycle for parallel programs.
shared objects, CREW protocols, distributed debugging, execution replay, parallel programming, program instrumentation

J. Mellor-Crummey and T. Leblanc, "Debugging Parallel Programs with Instant Replay," in IEEE Transactions on Computers, vol. 36, no. , pp. 471-482, 1987.
89 ms
(Ver 3.3 (11022016))