Historical Software Diagnostics using Lightweight Process Snapshots

• US 20150127991A1
• Filed: 12/08/2014
• Published: 05/07/2015
• Est. Priority Date: 08/04/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Davis, Jackson, Kim, Tae Hyung, Thomsen, Colin A., Carroll, Steve
• Granted Patent: US 10,324,823 B2
• Time in Patent Office: Days
• US Class Current: 714/38.11
• CPC Class Codes: G06F 11/3096 wherein the means or processing minimize the use of computing system or of computing system component resources, e.g. non-intrusive monitoring which minimizes the probe effect: sniffing, intercepting, indirectly deriving the monitored data from other directly available data
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Abstract

A debugging and diagnostics system allows users to take lightweight process snapshots of running debuggee processes so the users may analyze those snapshots at a later time. The snapshot mechanism allows debugging tools to compare an original process or one or more process snapshots or to compare any of a series of snapshots to each other. The snapshot mechanism further allows users to inspect a snapshot of process memory while allowing the original process to continue running with minimal impact. A user may do historical debugging using process snapshots of a debuggee process taken over time. This allows the user to view the state of the debuggee process as it existed when the snapshot was taken. The lightweight process snapshot is less invasive because it does not require a full copy of the memory and allows the original process to run un-interrupted while specific collections and inspections are completed.

Claims

1. In a computing environment, a method of debugging an executing process, the method comprising:

running, independently, an executing process and a snapshot of the executing process; and

analyzing data collected from the snapshot, using a debugging tool associated with the snapshot, without affecting the executing process.

2. The computer-implemented method of claim 1, wherein the snapshot is automatically generated based on occurrence of an event.

3. The computer-implemented method of claim 1, further comprising:

generating the snapshot of the executing process, wherein the execution of the executing process is continued after generating the snapshot.

4. The computer-implemented method of claim 1, further comprising:

collecting the data from the snapshot.

5. The computer-implemented method of claim 1, wherein the snapshot comprises a copy of current data in memory addresses of the executing process.

6. The computer-implemented method of claim 1, wherein the snapshot of the executing process is generated at predetermined times.

7. The computer-implemented method of claim 1, further comprising:

generating a plurality of snapshots based on satisfaction of conditions provided by a user using the debugging tool.

8. The computer-implemented method of claim 1, wherein the data collected in the snapshot comprises call stacks and variable values.

9. The computer-implemented method of claim 1, wherein the execution of the executing process is continued after generating the snapshot.

10. The computer-implemented method of claim 1, further comprising:

debugging the executing process by analyzing the data collected in the snapshot while allowing the executing process to run.

11. The computer-implemented method of claim 1, further comprising:

displaying data captured in the snapshot in a user interface.

12. A computer-readable storage device comprising instructions that, when executed by a computer, cause the computer system to:

independently run an executing process and a process snapshot of the executing process; and

analyze data collected from the process snapshot, using a debugging tool associated with the process snapshot, without affecting the executing process.

13. The computer-readable storage device of claim 12, wherein the process snapshot is automatically generated based on occurrence of an event.

14. The computer-readable storage device of claim 12, further comprising:

generate the snapshot of the executing process, wherein the execution of the executing process is continued after generating the process snapshot.

15. The computer-readable storage device of claim 12, further comprising:

collect the data from the process snapshot.

16. The computer-readable storage device of claim 12, wherein the process snapshot comprises a copy of current data in memory addresses of the executing process.

17. A computer system comprising:

a memory and a processor configured to utilize instructions in the memory to implement a method for debugging an executing process, the computer system configured to;

run, independently, the executing process and a snapshot of the executing process; and

analyze data collected from the snapshot, using a debugging tool associated with the snapshot, without affecting the executing process.

18. The computer system of claim 17, further comprising:

generate the snapshot of the executing process, wherein the execution of the executing process is continued after generating the snapshot.

19. The computer system of claim 17, wherein the snapshot comprises a copy of current data in memory addresses of the executing process.

20. The computer system of claim 17, further configured to:

collect the data from the snapshot.