Method of walking-up a call stack for a client/server program that uses remote procedure call

• US 5,970,248 A
• Filed: 07/13/1998
• Issued: 10/19/1999
• Est. Priority Date: 09/29/1994
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Meier, Michael S.
• Primary Examiner(s): Hafiz, Tariq R.
• Assistant Examiner(s): Chavis, John Q.
• Application Number:
  US09/114,709
• Time in Patent Office: 463 Days
• Field of Search: 395/704
• US Class Current: 717/125
• CPC Class Codes: G06F 11/3632 of specific synchronisation aspects
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services

Abstract

When displaying the caller stack of a distributed client/server program that uses Remote Procedure Calls (RPC), the user is provided the capability of viewing the RPC calls in the same manner as normal procedure calls. When a breakpoint is encountered in an RPC server program while using a debugger for distributed programs, the call stacks for the client and server program are appended together into a single distributed call stack. In the case of nested RPC calls (e.g. program A executes an RPC call to program B which executes an RPC call to C and so on) all of the call stacks are appended together in the order they were created. The distributed call stack may span many programs, threads of execution, and computing machines. The distributed call stack may be used to select a routine from the call stack when setting a context for a tool that displays program state information. For example, when the user selects a particular routine from the distributed call stack, the source listing, variables that are currently in scope, and thread executing the routine may be shown in various display windows.

Claims

1. A method for debugging a distributed computer program comprising a client program executing on a first portion of a distributed data processing system and a server program executing on a second portion of the distributed data processing system, said method comprising the steps of:

(a) determining a first call stack on the first portion of the distributed data processing system of the client program by use of a debugger;

(b) determining a second call stack on the second portion of the distributed data processing system of the server program by use of the debugger; and

(c) appending the first call stack and second call stack together on the first portion of the distributed data processing system to form a single distributed call stack.

2. The method of claim 1 further comprising the step of displaying on the first portion of the distributed data processing system the single distributed call stack.

3. The method of claim 1 further comprising the step of:

determining the second call stack on the second portion of the distributed data processing system of the server program by evaluating remote procedure call (RPC) run-time data structures.

4. The method of claim 3 further comprising the steps of:

(a) setting a current context to a context where a breakpoint occurs;

(b) walking up a call stack of the current context;

(c) for each routine in the current context call stack, determining if it is a server dispatch routine, and

if it'"'"'s not a server dispatch routine, outputting the program name and continuing up the current context call stack, and

if it is a server dispatch routine, obtaining a context of a client dispatched by the server dispatch routine, and setting the current context to the context of the dispatched client;

(d) walking up a call stack of the current context of the dispatched client; and

(e) for each routine in the call stack of the current context of the dispatched client, determining if it is a client call, and if it is a client call, looping back to step (a).

5. A distributed data processing system for debugging a distributed computer program comprising a client program executing on a first portion of a distributed data processing system and a server program executing on a second portion of the distributed data processing system, said distributed data processing system comprising:

(a) means for determining a first call stack on the first portion of the distributed data processing system of the client program by use of a debugger;

(b) means for determining a second call stack on the second portion of the distributed data processing system of the server program by use of the debugger; and

(c) means for appending the first call stack and second call stack together on the first portion of the distributed data processing system to form a single distributed call stack.

6. The system of claim 5 further comprising means for displaying on the first portion of the distributed data processing system the single distributed call stack.

7. The system of claim 5 further comprising:

means for determining the second call stack on the second portion of the distributed data processing system of the server program by evaluating remote procedure call (RPC) run-time data structures.

8. The system of claim 7 further comprising:

(a) means for setting a current context to a context where a breakpoint occurs;

(b) means for walking up a call stack of the current context;

(c) means for determining for each routine in the current context call stack, if it is a server dispatch routine, and

if it'"'"'s not a server dispatch routine, means for outputting the program name and continuing up the current context call stack, and

if it is a server dispatch routine, means for obtaining a context of a client dispatched by the server dispatch routine, and setting the current context to the context of the dispatched client;

(d) means for walking up a call stack of the current context of the dispatched client; and

(e) means for determining for each routine in the call stack of the current context of the dispatched client, if it is a client call, and if it is a client call, means for looping back to means (a).

9. An article of manufacture for use in a distributed data processing system for debugging a distributed computer program comprising a client program executing on a first portion of a distributed data processing system and a server program executing on a second portion of the distributed data processing system, said article of manufacture comprising a computer-readable storage medium having a computer program embodied in said medium which causes the distributed data processing system to:

(a) determine a first call stack on the first portion of the distributed data processing system of the client program by use of a debugger;

(b) determine a second call stack on the second portion of the distributed data processing system of the server program by use of the debugger; and

(c) append the first call stack and second call stack together on the first portion of the distributed data processing system to form a single distributed call stack.

10. The article of manufacture of claim 9 wherein said computer program further causes the distributed data processing system to display on the first portion of the distributed data processing system the single distributed call stack.

11. The article of manufacture of claim 9 wherein said computer program further causes the distributed data processing system to:

determine the second call stack on the second portion of the distributed data processing system of the server program by evaluating remote procedure call (RPC) run-time data structures.

12. The article of manufacture of claim 11 wherein said computer program further causes the distributed data processing system to:

(a) set a current context to a context where a breakpoint occurs;

(b) walk up a call stack of the current context;

(c) determine for each routine in the current context call stack, if it is a server dispatch routine, and

if it'"'"'s not a server dispatch routine, output the program name and continue up the current context call stack, and

if it is a server dispatch routine, obtain a context of a client dispatched by the server dispatch routine, and set the current context to the context of the dispatched client;

(d) walk up a call stack of the current context of the dispatched client; and

(e) determine for each routine in the call stack of the current context of the dispatched client, if it is a client call, and if it is a client call, loop back to (a).