Dbxtool: A window‐based symbolic debugger for sun workstations

Adams, Evan; Muchnick, Steven S.

doi:10.1002/spe.4380160705

Cited by 44 publications

(11 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This is usually accomplished by supporting multiple debugger windows, one per process [15,16,171. Even with serial debugging, it is difficult for the user to correlate changes in program state with his/her concept of what correct program behavior should be.…”

Section: Types Of Visualization Systemsmentioning

confidence: 99%

Models for visualization in parallel debuggers

Pancake

Utter

1989

Proceedings of the 1989 ACM/IEEE Conference on Supercomputing - Supercomputing '89

View full text Add to dashboard Cite

Section: Types Of Visualization Systemsmentioning

confidence: 99%

Models for visualization in parallel debuggers

Pancake

Utter

1989

Proceedings of the 1989 ACM/IEEE Conference on Supercomputing - Supercomputing '89

View full text Add to dashboard Cite

“…Context-free grammars have been used by Banau and Lenorovitz [9], and Olsen [18,19]. The Input Tools notation of Van den Bos [21] can in some sense be considered a cross between event handlers and CFG notations.…”

Section: Previous Workmentioning

confidence: 99%

A grammar-based approach to automatic generation of user-interface dialogues

Scott

Yap

1988

Proceedings of the SIGCHI Conference on Human Factors in Computing Systems - CHI '88

View full text Add to dashboard Cite

An effective user interface requires a dialogue layer that can handle multiple threads of interaction simultaneously. We propose a notation for specifying dialogues based on context-free attributed grammars with two extensions: fork operators for specifying sub-dialogues and co&e& attributes for dispatching tokens. The notation is useful both as a means of communicating the behavior of the dialogue layer to designers and as input to a dialogue compiler that generates program code. In this paper we explain the motivation for our work and provide practical examples of the use of fork and context. In addition, we outline algorithms for parsing and for generating parser tables.

show abstract

“…Therefore, it is much easier to make use of the tracing capability of symbolic debuggers. With windowbased symbolic debuggers, specifying line numbers can easily be done by clicking lines with a mouse [2].…”

Section: Introductionmentioning

confidence: 99%

Automatic resumption mechanism for program debugging

Shimomura

1991

SIGSOFT Softw. Eng. Notes

View full text Add to dashboard Cite

In program debugging, tracing control instructions that examine internal program states can be saved in a file and this file can be used to initialize the debugging environment when a program is loaded by a debugger. When a source program is modified because of bugs, however, source line numbers are also changed. It is therefore necessary to update the source line numbers in a tracing control instruction file according to the modifications in the source program. This paper proposes a solution by means of an automatic resumption mechanism that simplifies the debugging procedure from source modification to the beginning of the next debugging. While a programmer is creating an executable program using make after he has modified the program, the tracing control instruction file is updated automatically, so the programmer does not even have to think of updating them. This mechanism makes it very easy to resume debugging with the same debugging environment after program modification.

show abstract

Dbxtool: A window‐based symbolic debugger for sun workstations

Cited by 44 publications

References 4 publications

Models for visualization in parallel debuggers

Models for visualization in parallel debuggers

A grammar-based approach to automatic generation of user-interface dialogues

Automatic resumption mechanism for program debugging

Contact Info

Product

Resources

About