| C. L. Jeffery, Monitoring and Visualizing Program Execution: an Exploratory Approach, Ph.D Dissertation, 1993. |
....is also contributes to the kind and level of monitoring that is possible. Many instrumentation systems are quite low level, reporting machine level information. On the other extreme, an instrumentation system can report high level information such as the access or manipulation of a link list [Jeff93]. The goal of CCI is to be able to extract from the C programming language, information similar to the high level information available from monitoring languages like Icon or other high level interpretive languages. 1.4.1 Run time Instrumentation DBX [Lint90] a typical source level debugger, ....
....The monitor and the target program run concurrently and information is transferred in the form of events using light weight context switches. Quite a few execution monitoring tools have been developed and have been used successfully to find bugs that would have been difficult to find otherwise [Jeff93]. 1.4.5 Goals of this Research The related work points to the fact that there is a need for more advanced methods of debugging and visualization. It is also important to reduce intrusion and minimize the run time performance effects of instrumentation. These observations motivate CCI s goals: 1. ....
C. L. Jeffery, Monitoring and Visualizing Program Execution: an Exploratory Approach, Ph.D Dissertation, 1993.
....about a program s execution. 4 1.2 Problems faced when writing visualization tools Writing efficient visualization tools for monitoring the execution of a program is a complex task. The major problems encountered in obtaining execution information are volume, intrusion [Henr90] and access. [Jeff93] has detailed descriptions of those problems. Here we only emphasize that efficient gathering of information and processing large amounts of data without obscuring items of interest is the basis for a good execution monitoring tool. Also a good execution monitoring tool should be able to minimize ....
....of the Alamo framework is to reduce the difficulties in writing monitoring tools by constructing a platform on which monitor construction is relatively easier. Alamo stands for A Lightweight Architecture for MOnitoring. Alamo s design extends earlier work developed for an interpretive language [Jeff93] by developing techniques suitable for a compiled systems programming language, ANSI C. Applications of this framework can be in a variety of areas. Execution monitoring tools developed using this framework can help programmers in debugging their programs, performance tuning their programs, ....
[Article contains additional citation context not shown here]
C. L. Jeffery, Monitoring and Visualizing Program Execution: an Exploratory Approach, Ph.D Dissertation, 1993.
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