Browse Prior Art Database

Packaging Scheme for Bound Service Program in Operating System

IP.com Disclosure Number: IPCOM000106069D
Original Publication Date: 1993-Sep-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Gordhamer, SL: AUTHOR [+4]

Abstract

A method for facilitating the writing of debuggers will be disclosed. A set of application programming interfaces (API), which can be called by any application program, will be discussed. These APIs enable any programmer to easily write a debugger, allowing specialized debuggers for various applications to be written.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Packaging Scheme for Bound Service Program in Operating System

      A method for facilitating the writing of debuggers will be
disclosed.  A set of application programming interfaces (API), which
can be called by any application program, will be discussed.  These
APIs enable any programmer to easily write a debugger, allowing
specialized debuggers for various applications to be written.

Debug services are packaged as a bindable "service program".  The
services or APIs can then be invoked like functions in the run-time
library of a compiler.

Normally, to write a debugger, it is necessary to understand the
layout of a program on the system, know how the symbol table and
other debug data is stored in that program, and write an interface
into this data.

A set of program-callable interfaces have been written which allow
any programmer without specific knowledge of the internals of a
program to write a debugger.  These interfaces cover all aspects
essential in debugging a program, and they are written at a high
level.  The aspects of the debug process include:

o     adding of breakpoints and conditional breakpoints
o     stepping through a program
o     obtaining values of variables and expressions
o     changing of variables
o     determining the type of variables and the layout of structures
o     retrieving of source text and other textual views associated
    with
         the program

      A short description of each API follows:

1.  Start Source Debug-This API puts the job in debug mode and
indicates to the system which program is to be called when a
breakpoint or other debug event occurs.

2.  End Source Debug-This ends debug mode.

3.  Retrieve Module Views-This lists all the "views" in a module.  A
view is text associated with a module that is displayed by the
debugger when showing the source.  Compilers are free to create as
many views of the source code as desired.

4.  Register Debug View-Indicates to the system that this view is to
be used when debugging the module.

5.  Remove Debug View-Used when the view is no longer to be used.

6.  Retrieve Stopped Position-Indicates where in a...