Data triggered trace technique for debugging software programs

• US 5,870,606 A
• Filed: 05/01/1996
• Issued: 02/09/1999
• Est. Priority Date: 05/01/1996
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Lindsey, Anthony Hayden
• Primary Examiner(s): Trammell, James P.
• Assistant Examiner(s): Chaki, Kakali
• Application Number:
  US08/641,666
• Time in Patent Office: 1,014 Days
• Field of Search: 395/701, 395/704, 395/183.21, 395/183.15, 395/183.14, 395/183.11
• US Class Current: 717/128
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program

Abstract

A technique for permitting tracepoints to be set relative to data elements for the debugging of a procedural program is disclosed. A proxy object is provided for each data element relative to which tracing is desired. The proxy object intercepts messages sent from the program to the data element caused by the execution of logic statements. In accordance with a developer'"'"'s specified parameters, tracing functions relative to the data element are invoked in response to the receipt of each message dependent upon the nature of the message. The proxy object then forwards the message to the intended data element. Subsequent return of control from the data element to the program may also invoke the proxy object and affect tracing in accordance with parameters supplied by the developer to the debugger.

Claims

1. Computer readable code stored on media for triggering the creation of trace data based on access to a data element associated with a computer program, comprising:

first subprocesses for designating a data element relative to which trace data is desired; and

second subprocesses for initiating collection of trace data upon an attempt to access the designated data element.

2. Computer readable code stored on media for triggering the creation of trace data according to claim 1, wherein said first subprocesses further designate an event upon which the collection of trace data will cease, said computer readable code further comprising third subprocesses for causing the collection of trace data to cease upon occurrence of the designated event.

3. Computer readable code stored on media for triggering the creation of trace data according to claim 1, further comprising fourth subprocesses for designating a type of access for triggering the collection of trace data, wherein said second subprocesses initiate the collection of trace data when an attempt to access the designated data element is the designated type of access.

4. Computer readable code stored on media for triggering the creation of trace data according to claim 1, further comprising fifth subprocesses for modifying the collection of trace data after the access of the data element.

8. Computer readable code stored on media for triggering the creation of trace data according to claim 1, wherein said first subprocesses further comprises creating a proxy object for the designated data element and modifying the computer program so that messages intended for the data element are sent to the proxy object, and wherein said second subprocesses further comprises initiating collection of trace data when a message intended for the designated data element is received by the proxy object.

9. Computer readable code stored on media for triggering the creation of trace data according to claim 8, wherein the proxy object forwards all messages it receives which are intended for the designated data element to the designated data element.

5. In a computing environment, a system for collecting trace data based on accessing a data element associated with a computer program, comprising:

means for designating at least one data element relative to which collecting of trace data is desired;

means for designating tracing parameters; and

means for collecting trace data in accordance with the designated tracing parameters upon an attempt to access the designated data element or after accessing the designated data element.

6. A system for collecting trace data according to claim 5, further comprising means for ending collection of trace data based upon occurrence of an event designated in the tracing parameters.

7. A system for collecting trace data according to claim 5, wherein said designating means further comprises creating a proxy object corresponding to the designated data element and modifying the computer program to send all messages intended for the designated data element to the proxy object, the proxy object being programmed to forward messages it receives to the corresponding designated data element.

10. A method for collecting trace data based upon access of a data element in a computer program, comprising the steps of:

designating a data element relative to which collection of trace data is desired;

creating a proxy object to receive all access attempts of the designated data element;

modifying the computer program to send all attempts to access the designated data element to the proxy object; and

initiating collection of trace data upon an attempt to access the designated data element.

11. A method for collecting trace data according to claim 10, further comprising the step of designating tracing parameters, wherein said initiating step initiates collection of trace data when the designated tracing parameters are met.