MAPPING DYNAMIC ANALYSIS DATA TO SOURCE CODE

• US 20180260304A1
• Filed: 03/09/2017
• Published: 09/13/2018
• Est. Priority Date: 03/09/2017
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: MATOUSEK, TOMAS, HAMBY, JOHN LAWRENCE, JAYASWAL, MANISH KUMAR, CASEY, ANDREW MICHAEL
• Granted Patent: US 10,642,714 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 11/3612 by runtime analysis performance monitoring G06F11/3466
• CPC Class Codes: G06F 11/3624 by performing operations on the source code, e.g. via a compiler
• CPC Class Codes: G06F 11/3644 by instrumenting at runtime

Abstract

Metadata tables can provide the link between the instrumentation information collected and the location in the source code of the programming language construct that was instrumented. The metadata tables enable the relationship between the programming construct in the source code and the dynamic analysis information collected to be exact rather than an estimate. During compilation information is collected that enables a mapping between document table and analysis table to occur.

Claims

1. A front-end compiler, comprising:

an instrumenting module configured to;

receive information identifying at least one programming construct in a source code file;

receive the instrumentation to be performed on the at least one programming construct in the source code file;

insert the instrumentation into a representation of the source code file;

insert into a document table an identifier of the source code file and a location in the source code file comprising a location at which the at least one programming construct was found in the source code file;

collect dynamic analysis information for the instrumented programming language construct at execution;

store the collected dynamic analysis information for the instrumented programming construct in an analysis table indexed by the location at which the at least one programming construct was found in the source code file; and

match an index of the document table and an index of the analysis table to provide an exact location in the source code file of the instrumented programming language construct from which the collected dynamic analysis information was generated.

2. The instrumenting module of claim 1, wherein the document table comprises a source code file identifier.

3. The instrumenting module of claim 1, wherein the location in the source code file comprises a character position.

4. The instrumenting module of claim 3, wherein the location comprises a line and a column.

5. The instrumenting module of claim 3, wherein the location comprises a character offset from start of file.

7. The instrumenting module of claim 1, wherein an element N in the document table corresponding to a method M describes a text span for an instrumentation point represented by element N in an analysis table for the method M.

8. The instrumenting module of claim, 1 wherein an instrumentation point receives a sequential number.

6. (canceled)

9. A method of matching analysis data to a location in a source code program comprising:

receiving a document table, the document table comprising an identifier of a source code program, a method, and a text span representing a location of a programming language construct in the source code program, the programming language construct comprising an instrumented programming language construct;

storing dynamic analysis data collected during execution of the instrumented programming language construct in an analysis table indexed by instrumentation point;

matching an index of the document table and an index of the analysis table to determine an exact location of the programming language construct in the source code program; and

providing an exact location of the instrumented programming language construct in the source code program from which the dynamic analysis was generated.

10. The method of claim 9, wherein the document table comprises a source code identifier, a method name and location information for the programming language construct in the source code program, the programming language construct instrumented at compile time.

11. The method of claim 9, wherein a method in the source code program comprises a container for at least one programming language construct that is instrumented during compilation.

12. The method of claim 9, wherein each method is associated with a set of tables, a set of tables comprising a document table and an analysis table.

13. The method of claim 9, wherein each method is associated with a plurality of sets of tables, each set comprising a document table and an analysis table.

14. The method of claim 9, further comprising updating the analysis table, comprising dynamic analysis information collected during execution of a binary created from the source code program.

15. A device for exactly matching analysis results with location of a programming language construct in a source code file comprising:

a memory;

a processor, the processor configured to;

match instrumentation data collected at runtime to an exact location in the source code at which a programming language construct that was instrumented at compile time is found by;

inserting into a document table an identifier of the source code file and a location in the source code file at which the at least one programming construct was found in the source code file;

collecting dynamic analysis information for the instrumented programming language construct at execution;

storing the collected dynamic analysis information for the instrumented programming construct in an analysis table indexed by the location at which the at least one programming construct was found in the source code file; and

providing the exact location of the programming language construct in the source code file for the collected dynamic analysis information.

16. The device of claim 15, wherein the processor is further configured to:

receive a document table.

17. The device of claim 16, wherein the processor is further configured to:

store instrumentation data collected at runtime in the analysis table.

18. The device of claim 17, wherein the processor is further configured to:

use an index for the instrumentation data in the analysis table as the index into the document table to retrieve an exact location of the programming language construct in the source code, the programming language construct instrumented at compile time.

19. The device of claim 15, wherein the processor is further configured to provide:

a text span in the source code file at which the programming language construct is found.

20. The device of claim 15, wherein the processor is further configured to map instrumentation results to a location in a source code using a document table and an analysis table.