1984ACM SIGPLAN NoticesRequires access

Screen-oriented highlevel debugger (SHD) for Pascal

Vijay K. Garg

Open publisher page 5 citations

Abstract

There are certain golden maxims in programming. One of them is, that no matter how meticulous a programmer is, he spends major portion of his software development time on debugging. In such wise, we must have good debuggers to reduce debugging time. As Lauesen[1] puts it, the superiority of a debugger lies in helping user catch more bugs in given time. Accordingly, power of a debugger is the sole yardstick for goodness of it. Power in this context mean both, functionality and convenience. Other factors, such as, extra information it requires from compiler, its bigger size etc. are irrelevant so long as it is extra powerful. The compexity of the debugger, in terms of efforts required to program it should not be a prohibiting factor either. A debugger is used, as often as, if not more than the compiler itself. Conventional Debuggers[2] which call themselves 'High Level Debugger' are no doubt better than 'Dumpers' but are still too primitive to help user in any substantial manner. Most of them are confined to setting up of breakpoints and examination of unstructured variables. SHD strives to match its level of commands with the thought process of the user for maximum efficiency in detecting bugs.

About this research paper

What this paper is about

There are certain golden maxims in programming. One of them is, that no matter how meticulous a programmer is, he spends major portion of his software development time on debugging. In such wise, we must have good debuggers to reduce debugging time. As Lauesen[1] puts it, the superiority of a debugger lies in helping user catch more bugs in given time. Accordingly, power of a debugger is the sole yardstick for goodness of it. Power in this context mean both, functionality and convenience. Other factors, such as, extra information it requires from compiler, its bigger size etc. are irrelevant so long as it is extra powerful. The compexity of the debugger, in terms of efforts required to program it should not be a prohibiting factor either. A debugger is used, as often as, if not more than the compiler itself. Conventional Debuggers[2] which call themselves 'High Level Debugger' are no doubt better than 'Dumpers' but are still too primitive to help user in any substantial manner. Most of them are confined to setting up of breakpoints and examination of unstructured variables. SHD strives to match its level of commands with the thought process of the user for maximum efficiency in detecting bugs.

Why it matters

OpenAlex reports 5 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

There are certain golden maxims in programming. One of them is, that no matter how meticulous a programmer is, he spends major portion of his software development time on debugging. In such wise, we must have good debuggers to reduce debugging time. As Lauesen[1] puts it, the superiority of a debugger lies in helping user catch more bugs in given time. Accordingly, power of a debugger is the sole yardstick for goodness of it. Power in this context mean both, functionality and convenience. Other factors, such as, extra information it requires from compiler, its bigger size etc. are irrelevant so long as it is extra powerful. The compexity of the debugger, in terms of efforts required to program it should not be a prohibiting factor either. A debugger is used, as often as, if not more than the compiler itself. Conventional Debuggers[2] which call themselves 'High Level Debugger' are no doubt better than 'Dumpers' but are still too primitive to help user in any substantial manner. Most of them are confined to setting up of breakpoints and examination of unstructured variables. SHD strives to match its level of commands with the thought process of the user for maximum efficiency in detecting bugs.

Key concepts: Debugger, Computer science, Debugging, Programming language, Programmer, Compiler, Algorithmic program debugging, Pascal (unit)

Related papers

Back to paper searchBrowse research topicsOriginal source
Screen-oriented highlevel debugger (SHD) for Pascal — Research Paper | ScholarLens