Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

ENVIRONMENT CAPTURE FOR DEBUG

IP.com Disclosure Number: IPCOM000007038D
Original Publication Date: 1993-Oct-01
Included in the Prior Art Database: 2002-Feb-20
Document File: 1 page(s) / 75K

Publishing Venue

Motorola

Related People

J. Allan Toogood: AUTHOR [+2]

Abstract

The computing world has changed from a cen- tral computing environment to a distributed com- puting environment. When the computing platform of the user and the computing platform of the sot?- ware author are geographical and electronically separated, capturing the program data and environ- ment that causes the sohware to fail is difficult. Before sofiware can be modified to handle this unexpected data or environment that causes the software to mal- function, that data and environment must be cap- tured and made available to software author.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Page 1 of 1

0 M

MOTOROLA INC. Technical Developments Volume 20 October 1993

ENVIRONMENT CAPTURE FOR DEBUG

by J. Allan Toogood and Robert C. Turner

THE PROBLEM: CAPTURING THE PROBLEM ON A REMOTE COMPUTING PLATFORM

  The computing world has changed from a cen- tral computing environment to a distributed com- puting environment. When the computing platform of the user and the computing platform of the sot?- ware author are geographical and electronically separated, capturing the program data and environ- ment that causes the sohware to fail is difficult. Before sofiware can be modified to handle this unexpected data or environment that causes the software to mal- function, that data and environment must be cap- tured and made available to software author.

SOLUTION

  As part of the sohware development process, the software author registers what data and system files are critical to debugging the system. Other informa- tion that is also registered is who will receive the problem report and what are the possible data connectivity routes. This information is stored and made available when a problem occurs. This infor- mation is not stored with the delivered software at the user's site, but at the software author's site.

  When a problem occurs at the user's site, the problem tracking system on the user's computer is executed. The problem tracking system contacts the developer's computer system. The sofiware on the user's computer system (user's machine) and the soft- ware on the developer's computer (developer's machine) then begin to exchange information. The user's machine requests registration information for

the malfunctioning software fro...