Browse Prior Art Database

Software Test Tool for Dynamically Tracing Code Activity

IP.com Disclosure Number: IPCOM000102239D
Original Publication Date: 1990-Nov-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 42K

Publishing Venue

IBM

Related People

Billingsley, RE: AUTHOR [+3]

Abstract

This article describes a method of eliminating the need for scaffold code used for debugging newly developed code on hardware.

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

Software Test Tool for Dynamically Tracing Code Activity

       This article describes a method of eliminating the need
for scaffold code used for debugging newly developed code on
hardware.

      Disclosed herein are a software method for simplifying debug
using an HP*64000 and also elimination of the need for scaffold code
for a more realistic test environment.  A small amount of code is
added to key code modules to store vital information about the
current code activity.  This information is stored in a fixed address
space which is not being used so that the HP64000 test tool can be
set up to trace only that address space.  The information which is
stored is described as follows:
     All incoming notes (timer, interrupt, request, confirm
     and response)
     All outgoing notes (indicate and confirm)
     State machine status
     Code entry address
     Control block addresses

      Each piece of information is preceded by a different flag to
give quick identification of which type of information is to follow.
For example, a flag of 'FFFFFFFF'XB is used to flag all incoming
notes.  This makes the HP64000 trace easy to use in determining what
the incoming notes and outgoing notes are and in what order they were
received or sent.  It also makes it easy to determine what the state
machine status is upon exiting the code.

      This information allows developers to debug code without having
to make several iterations of st...