Browse Prior Art Database

Mixed Mode State Saving for Object Oriented/Procedural Debugger

IP.com Disclosure Number: IPCOM000112300D
Original Publication Date: 1994-Apr-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 25K

Publishing Venue

IBM

Related People

Coskun, N: AUTHOR [+2]

Abstract

There are almost no debuggers that work in both object oriented and procedural modes. This is a problem with SOM, which is an object model that works with procedural method implementations.

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

Mixed Mode State Saving for Object Oriented/Procedural Debugger

      There are almost no debuggers that work in both object oriented
and procedural modes.  This is a problem with SOM, which is an object
model that works with procedural method implementations.

      With object oriented debuggers the state combines the instance
variables location within a method and the "event path".  The event
path is a combination of the events that have been nested or stacked
to get to the current state.  This information is readily available,
and can easily be saved within the context of a debugger.

      The state within a current method is a combination of local and
global variable values, combined with the current program stack and
the instruction pointer.  This information is saved by current
procedural debuggers.  This problem can be easily solved by providing
an interface that lets the object oriented debugger call the
procedural debugger, and asking it to save this information in the
traditional way.