Browse Prior Art Database

Method Of Performing Run Time Code Path Analysis

IP.com Disclosure Number: IPCOM000201829D
Publication Date: 2010-Nov-24
Document File: 4 page(s) / 100K

Publishing Venue

The IP.com Prior Art Database

Abstract

A method is provided for analyzing a program code to capture and document code path of the program code at run time. The method locates and sorts module names, module addresses, and module lengths corresponding to the program code and uses the module names, the module addresses, and the module lengths to start a tracing facility. A test case suite is then started and trace data is captured. Thereafter, an annotated listing is produced using the captured trace data, the module names, the module addresses, and the module lengths.

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

Page 01 of 4

Method Of Performing Run Time Code Path Analysis

Disclosed is a method of analyzing a program code to capture and document code path of the program code at run time.

The method disclosed herein captures and documents code path for program codes. In this case, a code path corresponding to a command, a set of commands, or a test case, etc. may be captured at run time. The captured code paths are then used for code path analysis, code path documentation, high level or low level code path flow charts etc. The method involves locating and sorting module names, module addresses, and module lengths corresponding to the program code. The module names, the module addresses, and the module lengths are sorted in order of storage addresses. An exemplary table illustrating a sorted program code is shown in Fig. 1. On sorting the program code, a tracing facility is started using the module names, the module addresses, and the module lengths. An exemplary table illustrating a pseudo code for setting up a trace facility used to trace code execution is illustrated in Fig. 2. For example, in Fig. 2, a trace facility traces "MOD0CAX0" for a length of "hex 2D10".

(This page contains 00 pictures or other non-text object)

Figure 1


(This page contains 01 pictures or other non-text object)

Figure 2

Thereafter, a test case suite is started and trace data is captured. The trace data includes, for example executed instruction addresses, condition codes, control blocks and states at specified trace points. Fig. 3 exemplarily illustrates a pseudo code for capturing trace data such as, executed instructions and offsets, state condition codes, and control blocks a...