Browse Prior Art Database

Method for Single-Step Frame Debugging

IP.com Disclosure Number: IPCOM000100453D
Original Publication Date: 1990-Apr-01
Included in the Prior Art Database: 2005-Mar-15
Document File: 1 page(s) / 52K

Publishing Venue

IBM

Related People

Costin, D: AUTHOR [+3]

Abstract

This article describes a method for viewing and manipulating the single-step execution of the KnowledgeTool* debugger to control the execution of the frame commands over a seamless interface transparent to any currently executing application, said frame commands being applied to a frame manager portion of a cyclic, rule based, object sensitive production system for accessing a frame organized knowledge base of facts and rules, comprising the steps of: a. suspending any currently executing application; and b. applying a preselected command to the frame manager for interpretive execution over a path defined by a subroutine call, said path having an entry point the same as that used by the suspended application.

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

Method for Single-Step Frame Debugging

       This article describes a method for viewing and
manipulating the single-step execution of the KnowledgeTool* debugger
to control the execution of the frame commands over a seamless
interface transparent to any currently executing application, said
frame commands being applied to a frame manager portion of a cyclic,
rule based, object sensitive production system for accessing a frame
organized knowledge base of facts and rules, comprising the steps of:
      a.   suspending any currently executing application; and
      b.   applying a preselected command to the frame manager for
interpretive execution over a path defined by a subroutine call, said
path having an entry point the same as that used by the suspended
application.

      Anytime the KnowledgeTool debugger is available, commands may
also be sent to the Frame Manager (also referred to as frame
services).  These commands can query, create, destroy, or modify
frames.  The frame base can also be loaded, saved, or modified.
These actions may be transparent to the currently running
application.  The frames accessed may not be the same as those
accessed by this application.

      The commands sent to the Frame Manager are used to invoke an
interpretive interface.  This interface is a text only interface
unlike that available directly from the application.  The command
string is interpreted, and the unused portion is returned to the
debugger fo...