Autonomic execution tracking and correction of functions

• US 20050066311A1
• Filed: 06/24/2004
• Published: 03/24/2005
• Est. Priority Date: 09/22/2003
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Teich, Torsten, Schaal, Albert, Hagmeier, Joachim
• Application Number:
  US10/876,024
• Publication Number:
  US 20050066311A1
• Time in Patent Office: Days
• US Class Current: 717/128
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program

Abstract

The present invention relates to computing systems, and in particular to a method for tracking the execution of a computer program during execution thereof. In order to reduce errors or fraud in the execution flow of the program it is proposed to insert so-called trace code instructions (TCI) (220, 222, 224, 226, 228, 230) multiply into the program'"'"'s source code (20) in particular at crucial locations thereof. Said trace code when executed or interpreted in Interpreter-based programming languages—calculates some verification information, which can be used by checking its calculation results for determining if or if not the program execution path was the expected one. If an unexpected result occurs, predetermined, programmed measures can be undertaken according to the respective environment, application or security policy.

Claims

1. A method for tracking the execution of a computer program during execution thereof, characterized by the steps of:

a) executing additional program trace code instructions inserted in the source code of the program to be tracked in-between the regular instruction sequence given by the business target of the program;

b) said trace code instructions calculating verification information from program position information when executed;

c) comparing at least once during program execution; and

a run-time calculated verification information with a respective, pre-stored reference position information expected for regular execution of the program.

2. The method according to claim 1, in which the program position information can be selected from the following group of different types:

a) a counter variable;

b) an address information derived from the current execution position;

c) a checksum calculated over some predetermined or all previous program instructions;

d) a checksum calculated over some selected or all previous program addresses; and

e) other logical, arithmetical, procedural, statistical values.

3. The method according to claim 1, in which said trace code instructions are provided at code locations selected from the group:

a) before and/or after crucial regular instructions;

b) before and/or after branch instructions; and

c) before and/or after execution of a subroutine, function, and the like.

4. The method according to claim 1, in which said trace code instruction calculations are immediately followed by checking the verification information they calculated immediately before.

5. The method according to claim 1, in which the step of checking the verification information of a preceding trace code instructions is followed by the step of generating the current verification information.

6. The method according to claim 1, in which said trace code instructions include a calculation of current values of program variables.

7. The method according to claim 1, in which the program execution is repeated automatically after the verification step yielded unexpected verification information.

8. The method according to claim 1, in which after the verification step yielded unexpected verification information, predetermined measures are undertaken dependent of the actual security policy present in the respective application.

9. The method according to claim 1, in which during runtime of said program a dynamically selectable trace code generation routine is executed.

10. The method according to claim 1, in which said trace code generation routine is organized self-modifying dependent of predetermined runtime parameters.

11. The method according to claim 1, in which a default security code is included as trace code instruction, which can be overloaded by a respective updateable patch file.

12. A computer system having means for performing the steps of a method according to one of the preceding claims 1.

13. The computer system according to the preceding claim being a chip card.

16. A computer program product stored on a computer usable medium comprising computer readable program means for causing a computer to perform the method of anyone of the claims 1, when said computer program product is executed on a computer.

14. A computer program implementing a security-relevant application for execution in a data processing system and characterized by computer program code portions for performing the steps of:

a) executing additional program trace code instructions inserted in the source code of the program to be tracked in-between the regular instruction sequence given by the business target of the program;

b) said trace code instructions calculating verification information from program position information when executed; and

c) comparing at least once during program execution a run-time calculated verification information with a respective, pre-stored reference position information expected for regular execution of the program, when said computer program code portions are executed on a computer.

15. The computer program according to the preceding claim, wherein the program position information can be selected from the following group of different types:

a) a counter variable;

b) an address information derived from the current execution positions

c) a checksum calculated over some predetermined or all previous program instructions;

d) a checksum calculated over some selected or all previous program addresses; and

e) other logical, arithmetical, procedural, statistical values.