Visual device to assist computer program debugging

Interrupt status indicators allow computer programs to be debugged during checkout and provide a quick-look analysis for updating. Computer coupled indicator lamps and lamp driver circuitry register program malfunctions in priority interrupt controlled programs

Visualization designs for constraint logic programming

We address the design and implementation of visual paradigms for observing the execution of constraint logic programs, aiming at debugging, tuning and optimization, and teaching. We focus on the display of data in CLP executions, where representation for constrained variables and for the constrains themselves are seeked. Two tools, VIFID and TRIFID, exemplifying the devised depictions, have been implemented, and are used to showcase the usefulness of the visualizations developed

Interactive Virtual Debugger for GPSS/H

GPSS (General Purpose System Simulator) is a language, designed to aid the computer modeling and simulation of a wide variety of different real life systems. As with any other large programming project, debugging GPSS programs is unavoidable and often difficult. The present thesis describes an Interactive Visual Debugging System for GPSS/H which attempts to simplify the debugging task by allowing the programmer to observe the actual behavior of the model in simulated real time, while preserving all traditional interactive debugging tools - breakpoints, system traps, selective displays, etc. The present version of the Interactive Visual Debugger is developed for the UNIX operating system and is written in the ‘C’ programming language. The system can be readily used on all terminals capable of running the UNIX ‘curses’ library package. Because of its modular design, the system can be modified to accommodate additional terminal types, or to run under different operating systems

A methodology for the capture and analysis of hybrid data: a case study of program debugging

No description supplie

Inviwo -- A Visualization System with Usage Abstraction Levels

The complexity of today's visualization applications demands specific visualization systems tailored for the development of these applications. Frequently, such systems utilize levels of abstraction to improve the application development process, for instance by providing a data flow network editor. Unfortunately, these abstractions result in several issues, which need to be circumvented through an abstraction-centered system design. Often, a high level of abstraction hides low level details, which makes it difficult to directly access the underlying computing platform, which would be important to achieve an optimal performance. Therefore, we propose a layer structure developed for modern and sustainable visualization systems allowing developers to interact with all contained abstraction levels. We refer to this interaction capabilities as usage abstraction levels, since we target application developers with various levels of experience. We formulate the requirements for such a system, derive the desired architecture, and present how the concepts have been exemplary realized within the Inviwo visualization system. Furthermore, we address several specific challenges that arise during the realization of such a layered architecture, such as communication between different computing platforms, performance centered encapsulation, as well as layer-independent development by supporting cross layer documentation and debugging capabilities

Mining Sequences of Developer Interactions in Visual Studio for Usage Smells

In this paper, we present a semi-automatic approach for mining a large-scale dataset of IDE interactions to extract usage smells, i.e., inefficient IDE usage patterns exhibited by developers in the field. The approach outlined in this paper first mines frequent IDE usage patterns, filtered via a set of thresholds and by the authors, that are subsequently supported (or disputed) using a developer survey, in order to form usage smells. In contrast with conventional mining of IDE usage data, our approach identifies time-ordered sequences of developer actions that are exhibited by many developers in the field. This pattern mining workflow is resilient to the ample noise present in IDE datasets due to the mix of actions and events that these datasets typically contain. We identify usage patterns and smells that contribute to the understanding of the usability of Visual Studio for debugging, code search, and active file navigation, and, more broadly, to the understanding of developer behavior during these software development activities. Among our findings is the discovery that developers are reluctant to use conditional breakpoints when debugging, due to perceived IDE performance problems as well as due to the lack of error checking in specifying the conditional