Diagnostic workflow for production debugging

• US 9,612,939 B2
• Filed: 10/29/2014
• Issued: 04/04/2017
• Est. Priority Date: 10/29/2014
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Davis, Jackson
• Primary Examiner(s): Manoskey, Joseph D
• Application Number:
  US14/527,568
• Publication Number:
  US 20160124835A1
• Time in Patent Office: 888 Days
• Field of Search: 714 26, 714 25, 714 35, 714 381, 714 3811, 714 3813, 714 45
• CPC Class Codes: G06F 11/362 Software debugging
• CPC Class Codes: G06F 11/3636 by tracing the execution of the program
• CPC Class Codes: G06F 11/3644 by instrumenting at runtime
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A diagnostic workflow file can be used to control the future diagnostic actions taken by a debugger without user interaction with the debugger when it executes. The diagnostic workflow file is used by a debugger during a debug session. The debugger performs the actions directed by the diagnostic workflow file to simulate an interactive live debug session. The diagnostic workflow file can include conditional diagnostic operations whose execution depends on the state of program variables, diagnostic variables and diagnostic primitives in the debug session.

Claims

1. A system comprising:

at least one processor;

a memory connected to the at least one processor; and

a diagnostic tool comprising;

at least one program module loaded into the memory, the at least one program module creating a diagnostic workflow file, the diagnostic workflow file including instructions for controlling future diagnostic operations of a debugger without user interaction with the debugger as the debugger executes.

2. The system of claim 1, wherein the diagnostic workflow file comprises at least one conditional diagnostic operation.

3. The system of claim 1, wherein the diagnostic workflow file comprises at least one conditional diagnostic operation, wherein the conditional diagnostic operation is executed based on current state of an executing program.

4. The system of claim 3, wherein current state comprises a state of at least one diagnostic primitive.

5. The system of claim 4, wherein current state comprises a state of at least one diagnostic variable.

6. The system of claim 3, wherein current state comprises a state of at least one program variable.

7. The system of claim 1, wherein the conditional diagnostic operation is executed based on a combination of current state of:

a diagnostic primitive, a program variable and a diagnostic variable.

8. A method comprising:

receiving a diagnostic workflow file by a processor of a computing device, the diagnostic workflow file comprising instructions for controlling future diagnostic operations of a debugger without user interaction with the debugger as the debugger executes, the instructions including at least one conditional diagnostic operation wherein the conditional diagnostic operation is executed based on current state of at least one of;

a program variable, a diagnostic primitive and a diagnostic variable;

determining the current state of the at least one of;

a program variable, a diagnostic primitive and a diagnostic variable; and

collecting diagnostic information.

9. The method of claim 8, further comprising:

collecting diagnostic information by making a snapshot of process data.

10. The method of claim 8, further comprising:

displaying state of diagnostic information.

11. The method of claim 8, further comprising:

determining a state of a diagnostic primitive, the diagnostic primitive comprising one of creating a breakpoint, removing a breakpoint, enabling a breakpoint, disabling a breakpoint, changing a condition of a breakpoint, enabling an exception by type, disabling an exception by type, conditioning an exception based on a call stack the exception is thrown at, a debugger operation comprising a step operation.

12. The method of claim 8, further comprising:

determining a state of a diagnostic variable.

13. The method of claim 12, wherein a diagnostic variable comprises a variable used in debugging.

14. A device comprising:

at least one processor and a memory;

the at least one processor configured to;

use instructions provided in a diagnostic workflow file to automatically control diagnostic operations of an instrumented executable in a target process without user intervention with a debugger as the debugger executes; and

collect diagnostic information.

15. The device of claim 14, wherein the at least one processor is further configured to:

provide the diagnostic information to the debugger.

16. The device of claim 14, wherein the at least one processor is further configured to:

insert instrumented code into a function to generate an instrumented function while the target process executes.

17. The device of claim 14, wherein the at least one processor is further configured to:

determine state of a diagnostic primitive, the diagnostic primitive comprising one;

of creating a breakpoint, removing a breakpoint, enabling a breakpoint, disabling a breakpoint, changing a condition of a breakpoint, enabling an exception by type, disabling an exception by type, conditioning an exception based on a call stack at which the exception is thrown, a debugger operation comprising a step operation.

18. The device of claim 14, wherein the at least one processor is further configured to:

determine state of a diagnostic variable comprising a variable used in debugging.

19. The device of claim 14, wherein the at least one processor is further configured to:

determine current state of a diagnostic primitive.

20. The device of claim 14, wherein the at least one processor is further configured to:

determine state of a diagnostic variable referenced in the diagnostic workflow file.