Debugging concurrent programs
Citations Over TimeTop 1% of 1989 papers
Abstract
The main problems associated with debugging concurrent programs are increased complexity, the "probe effect," nonrepeatability, and the lack of a synchronized global clock. The probe effect refers to the fact that any attempt to observe the behavior of a distributed system may change the behavior of that system. For some parallel programs, different executions with the same data will result in different results even without any attempt to observe the behavior. Even when the behavior can be observed, in many systems the lack of a synchronized global clock makes the results of the observation difficult to interpret. This paper discusses these and other problems related to debugging concurrent programs and presents a survey of current techniques used in debugging concurrent programs. Systems using three general techniques are described: traditional or breakpoint style debuggers, event monitoring systems, and static analysis systems. In addition, techniques for limiting, organizing, and displaying a large amount of data produced by the debugging systems are discussed.
Related Papers
- → Debugging by asking questions about program output(2006)10 cited
- → High-level debugging with the aid of an incremental optimizer(2003)14 cited
- Study on Program Debugging in "Programming in C" Teaching(2010)
- On the Application of Heuristic Knowledge for Program Debugging(1999)
- Enhancing Trace Debugging with Algorithmic and Omniscient Debugging(2013)