Remote monitoring of computer programs

• US 5,918,004 A
• Filed: 06/03/1996
• Issued: 06/29/1999
• Est. Priority Date: 06/02/1995
• Status: Expired due to Term

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Rational Software Corp (International Business Machines Corporation)
• Inventors: Anderson, Mark D., Pan, Douglas, Bigall, Evan J., Hastings, Reed, Clifford, Christine, Sorensen, Jon
• Primary Examiner(s): HUA, LY
• Application Number:
  US08/657,106
• Time in Patent Office: 1,121 Days
• Field of Search: 395/183.01, 395/183.08, 395/183.11, 395/183.13, 395/183.14
• US Class Current: 714/38.13
• CPC Class Codes: G06F 11/0715 in a system implementing multitasking multitasking per se G06F9/46
• CPC Class Codes: G06F 11/2294 by remote test
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

Systems and methods for remotely monitoring the execution of computer programs are provided. Monitoring instructions are added the computer program so that during execution of the program, data may be collected regarding the program execution. The collected data may be automatically sent to a remote system or site for analysis. The monitoring instructions create little or no performance impact on the client yet provide valuable information to the developer of the program. Additionally, the monitoring instructions may be changes during computer program development.

Claims

1. In a computer system, a method of remotely monitoring execution of a computer program, comprising the steps of:

modifying the computer program to include at least one monitoring instruction for collecting data regarding the execution of the computer program;

executing the computer program;

the at least one monitoring instruction collecting data regarding the execution of the computer program; and

sending the collected data to a remote system.

2. The method of claim 1, further comprising the step of automatically sending the collected data to the remote system when the computer program finishes execution.

3. The method of claim 1, further comprising the step of changing the at least one monitoring instruction over the computer program development cycle.

4. The method of claim 1, further comprising the step of classifying the execution of the computer program as normal or abnormal.

5. The method of claim 4, further comprising the step of saving the call stack in the collected data if the execution of the computer program is classified as abnormal.

6. The method of claim 1, further comprising the step of allowing a user to customize processing that will be performed when the computer program finishes execution.

7. The method of claim 1, further comprising the step of generating a symbolic call stack on the remote system so that the computer program may be debugged remotely.

8. The method of claim 1, wherein the computer program is compiled on the remote system and further comprising the step of storing a module map when the computer program is compiled on the remote system.

9. The method of claim 8, further comprising the step of storing a call stack and module list when the computer program finishes execution.

10. The method of claim 9, further comprising the step of generating a module name/relative virtual address (RVA) list from the call stack and the module list.

11. The method of claim 10, further comprising the step of sending the module name/RVA list to the remote system.

12. The method of claim 11, further comprising the step of generating a symbolic call stack on the remote system from the module map and the module name/RVA list so that the computer program may be debugged remotely.

13. The method of claim 1, further comprising the step of remotely debugging the computer program.

14. The method of claim 1, further comprising the step of sending a version of the computer program to the remote system during execution of the computer program.

15. The method of claim 14, further comprising the step of downloading a new version of the computer program from the remote system.

16. The method of claim 1, further comprising the step of sending information to a bug tracking application.

17. The method of claim 1, further comprising the step of, for each portion of the computer program designed by a different vendor, collecting data specific to each portion.

18. The method of claim 1, wherein the at least one monitoring instruction specifies a vendor.

19. The method of claim 1, further comprising the step of adding the at least one monitoring instruction to source code of the computer program.

20. The method of claim 19, further comprising the step of utilizing a Windows hook to intercept a system call invoked by the computer program.

21. The method of claim 1, further comprising the step of augmenting object code of the computer program to include the at least one monitoring instruction.

22. The method of claim 1, wherein the at least one monitoring instructions are computer platform independent.

23. A distributed computer system, comprising:

a server computer;

a client computer in communication with the server computer; and

a computer program running on the client computer that has been modified to include at least one monitoring instruction that collects and sends data regarding execution of the computer program to the server computer.

24. The distributed computer system of claim 23, further comprising a transport medium connecting the client computer and the server computer.

25. The distributed computer system of claim 24, wherein the transport medium is a network or media.

26. The distributed computer system of claim 23, further comprising a dynamic-link library (DLL) for intercepting system calls.

27. The distributed computer system of claim 23, further comprising a bug tracking application.

28. The distributed computer system of claim 23, further comprising an expansion mechanism for augmenting the computer program to include the at least one monitoring instruction.

29. A computer program product for remotely monitoring execution of a computer program, comprising:

a computer readable storage medium storing the computer program comprising;

code that calls at least one monitoring instruction, the at least one monitoring instruction collecting data regarding the execution of the computer program; and

code that sends the collected data to a remote system.

30. The computer program product of claim 29, further comprising code that automatically sends the collected data to the remote system when the computer program finishes execution.

31. The computer program product of claim 29, further comprising code that classifies the execution of the computer program as normal or abnormal.

32. The computer program product of claim 29, further comprising code that saves the call stack in the collected data if the execution of the computer program is classified as abnormal.

33. The computer program product of claim 29, further comprising code that allows a user to customize processing that will be performed when the computer program finishes execution.

34. The computer program product of claim 29, further comprising code that stores a call stack and module list when the computer program finishes execution.

35. The computer program product of claim 34, further comprising code that generates a module name/relative virtual address (RVA) list from the call stack and the module list.

36. The computer program product of claim 35, further comprising code that sends the module name/RVA list to the remote system.

37. The computer program product of claim 29, further comprising code that downloads a version of the computer program from the remote system.

38. The computer program product of claim 29, further comprising code that sends information to a bug tracking application.

39. The computer program product of claim 29, wherein the at least one monitoring instruction specifies a vendor.

40. In a computer system, a method of remotely monitoring execution of a computer program, comprising:

modifying the computer program to include at least one monitoring instruction;

executing the computer program;

the at least one monitoring instruction saving a call stack and a module list of the computer program;

generating a module name/relative virtual address (RVA) list from the call stack and the module list; and

sending the module name/RVA list to a remote system.

41. The method of claim 40, further comprising generating a symbolic call stack on the remote system from a module map generated when the computer program was compiled and the module name/RVA list.

42. The method of claim 41, further comprising debugging the computer program on the remote system utilizing the symbolic call stack.

43. The method of claim 40, further comprising classifying the execution of the computer program as normal or abnormal.

44. The method of claim 43, wherein the module name/RVA list is automatically sent to the remote system if the execution of the computer program is classified as abnormal.

45. A computer program product for remotely monitoring execution of a computer program, comprising:

a computer readable storage medium storing the computer program comprising;

code that calls at least one monitoring instruction that saves a call stack and a module list of the computer program;

code that generates a module name/relative virtual address (RVA) list from the call stack and the module list; and

code that sends the module name/RVA list to a remote system.

46. The computer program product of claim 45, wherein the module name/RVA list is automatically sent to the remote system when the computer program finishes execution.

47. The computer program product of claim 45, further comprising code that classifies the execution of the computer program as normal or abnormal.

48. The computer program product of claim 47, wherein the module name/RVA list is automatically sent to the remote system if the execution of the computer program is classified as abnormal.