Journal Article10.1145/1006142.1006151
Interactive debug requirements
Rich Seidner,Nick Tindall +1 more
25
TL;DR: This is a market requirements statement for Interactive Debugging, the result of a collaboration between the GUIDE/SHARE Language Futures Task Force and IBM.
read more
Abstract: This is a market requirements statement for Interactive Debugging It is the result of a collaboration between the GUIDE/SHARE Language Futures Task Force (LFTF) and IBMThe LFTF was formed at meetings of SHARE and GUIDE in 1979 The objective of the task force was to provide IBM with the views of the user community on the future of the application development environment The Task force chose to limit its discussions primarily to "enhancements to the procedural languages and the environments in which they operate"
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Debugging concurrent programs
TL;DR: The main problems associated with debugging concurrent programs are increased complexity, the "probe effect", nonrepeatability, and the lack of a synchronized global clock as discussed by the authors, and a survey of debugging techniques can be found in this paper.
390
Monitoring and debugging distributed real-time programs
TL;DR: This paper describes how the monitor can be used to debug distributed and parallel applications by deterministic execution replay and presents a novel approach to monitoring shared variable references that provides transparent monitoring with low overhead.
86
DOC: a practical approach to source-level debugging of globally optimized code
D. S. Coutant,S. Meloy,M. Ruscetta +2 more
- 01 Jun 1988
TL;DR: DOC, a prototype solution for Debugging Optimized Code, is implemented, a modification of the existing C compiler and source-level symbolic debugger for the HP9000 Series 800 to show in an actual implementation that source- level debugging of globally optimized code is viable.
83
Comparison checking: an approach to avoid debugging of optimized code
Clara Jaramillo,Rajiv Gupta,Mary Lou Soffa +2 more
- 01 Oct 1999
TL;DR: In this article, a comparison checker is presented to avoid the debugging of optimized code through comparison checking, which can be used to identify where in the application program the differences occurred and what optimizations were involved.
•Dissertation
Generating program animators from programming language semantics
Dave Berry
- 01 Jan 1990
TL;DR: A theory of program animation based on formal semantics shows how an animator for a language can be generated from a formal specification of that language using a model of evaluation that is formally correct with respect to the semantics.
28