7 citations found. Retrieving documents...
Larry D. Wittie. Debugging distributed c programs by real time replay. In SIGPLAN/SIGOPS Workshop on Parallel and Distributed Debugging, pages 55-67, Madison, WI USA, May 1988.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Replaying Distributed Applications with RPVM - Lourenço, Cunha (1998)   (Correct)

....be identified: 1. Incremental replay systems using checkpointing techniques, so that the user may restart the program form intermediate points. The main drawback of such technique is the need to record a large amount of trace information to save the program state in the intermediary checkpoints [23] 2] 2. Other approaches require the user to replay the program from the beginning, but less information need to be included in the trace file, with the resulting smaller intrusion. In the data driven replay technique, all the data exchanged between processes is recorded. The control driven ....

Larry D. Wittie. Debugging distributed C programs by real time replay. Proceedings of the ACM SIGPLAN/SIGOPS Workshop on Parallel and Distributed Debugging, published in ACM SIGPLAN Notices, 24(1):57-- 67, January 1989.


An Extensible, Retargetable Debugger for Parallel Programs - May (1994)   (Correct)

....PPD does not attempt to prevent these races, but it does try to identify code in which they might occur. Choi and Stone [9] later extended the ideas in PPD by defining heuristics for trading the size of a program trace file against the time it takes to replay the program. Wittie s BugNet [52] and Pan and Linton s Recap [43] both combine checkpointing with an event log that helps to reproduce the execution of a program. In a checkpointing system, the program periodically stops and records the contents of shared variables, interprocess messages, and other synchronization data. This ....

Wittie, L. D. Debugging distributed C programs by real time replay. Proceedings of the ACM SIGPLAN/SIGOPS Workshop on Parallel and Distributed Debugging, published in ACM SIGPLAN Notices 24, 1 (January 1989), 57--67.


Scalable Visualization of Parallel Systems - Garcia, Hughey   (Correct)

....use. The main problem is that it is only available for the MasPar, so it is not portable. The ideas are tailored for SIMD machines, where synchronous execution simplifies many of the animation issues. Other systems Bugnet is a system for debugging distributed programs running on a Unix network [Wit89] It uses a monitoring facility to record interprocess communication and input output for all the executing processes. All the information is traced and timestamped, allowing the user to back up the execution in case of an error and replay the events leading to the error in almost the exact ....

Larry D. Wittie. Debugging distributed C programs by real time replay. SIGPLAN Notices, 24(1):57--67, January 1989.


A Survey of Support For Implementing Debuggers - Paxson (1990)   (1 citation)  (Correct)

....to shared objects. It does not provide a checkpointing facility, but by enforcing the locking order upon reexecution a degree of reproducibility is 13 The IGOR authors added a ualarm system call that generates a signal after a specified quantity of user CPU time has elapsed. obtained. Bugnet [43] logs each interprocess communication (IPC) message along with a timestamp. It assumes that IPC is all done with system provided services, and thus cannot deal with shared memory IPC. A global checkpoint is made every 15 to 30 seconds, resulting in about a 2 performance impact. During replay, ....

Larry D. Wittie. Debugging distributed C programs by real time replay. In Proceedings of the ACM SIGPLAN/SIGOPS Workshop on Parallel and Distributed Debugging [17].


A Debugger for Id - Caro (1993)   (Correct)

....are captured, different debuggers offer different facilities to manipulate the events. Some simply provide browsers so that the programmer can view the sequence of events, and from that, manually reconstruct the behavior of the errant program. Other systems, like Instant Replay [25] and Bugnet [35], take a more active role: they allow the programmer to back up an re execute (replay) a program from a particular point, but using the events gathered during execution, they guarantee that the order of execution during replay will be the same as when the program was run originally. This guarantee ....

Larry D. Wittie. Debugging Distributed C Programs by Real Time Replay. Proceedings of the ACM SIGPLAN/SIGOPS Workshop on Parallel and Distributed Debugging, published in ACM SIGPLAN Notices, 24(1):57--67, January 1989.


An Architecture for the - Notification Storage And   (Correct)

No context found.

Larry D. Wittie. Debugging distributed c programs by real time replay. In SIGPLAN/SIGOPS Workshop on Parallel and Distributed Debugging, pages 55-67, Madison, WI USA, May 1988.


Aspects and Taxonomy of Program Visualisation - Oudshoorn, Widjaja, Ellershaw (1996)   (Correct)

No context found.

L.D. Wittie. Debugging Distributed C Programs by Real Time Replay. ACM SIGPLAN Notices, 24(1):57--67, January 1989. Proceedings of the ACM SIGPLAN and SIGOPS Workshop on Parallel and Distributed Debugging.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC