Identifying a software developer based on debugging information
First Claim
1. A method for identifying a software developer based on debugging information, the method comprising:
- automatically identifying a developer of a line of source code stored by the developer in a source code repository;
determining a developer contact tag for the developer;
automatically tagging the line of source code with the developer contact tag associated with the developer;
compiling the line of source code into a set of executable code, the set of executable code comprising the developer contact tag in a format compatible for presentation with debug information produced from the executable code, the debug information comprising;
a line number of the line of source code that was last executed;
a function that includes the line of source code last executed; and
a function that will be called next;
generating a stack trace in response to a failure when compiling the source code, the stack trace comprising;
an identifier of the function that includes the line of source code;
a source code line number; and
the developer contact tag; and
determining the developer associated with the line of source code from the debug information by way of the developer contact tag.
2 Assignments
0 Petitions
Accused Products
Abstract
A solution for identifying a software developer based on debugging information includes an identification module configured to identify a developer of a line of source code, a determination module configured to determine a developer contact tag for the developer, an encoding module configured to encode the developer contact tag, a tagging module configured to automatically tag the line of source code with the developer contact tag associated with the developer. The solution also includes a debug module configured to provide debug information, a decoding module configured to decrypt the developer contact tag, and a presentation module configured to present the debug stack trace in human readable form.
-
Citations
19 Claims
-
1. A method for identifying a software developer based on debugging information, the method comprising:
-
automatically identifying a developer of a line of source code stored by the developer in a source code repository; determining a developer contact tag for the developer; automatically tagging the line of source code with the developer contact tag associated with the developer; compiling the line of source code into a set of executable code, the set of executable code comprising the developer contact tag in a format compatible for presentation with debug information produced from the executable code, the debug information comprising; a line number of the line of source code that was last executed; a function that includes the line of source code last executed; and a function that will be called next; generating a stack trace in response to a failure when compiling the source code, the stack trace comprising; an identifier of the function that includes the line of source code; a source code line number; and the developer contact tag; and determining the developer associated with the line of source code from the debug information by way of the developer contact tag. - View Dependent Claims (2, 3, 4, 5, 6)
-
-
7. An apparatus for identifying a software developer based on debugging information, the apparatus comprising:
-
a display device; an identification module configured to identify one or more lines of source code as modified lines of source code by comparing a current set of source code provided by a developer to a previous version of the source code and configured to identify the developer of the modified lines of source code, the module comprising; a determination module configured to determine a developer contact tag for the developer; an encoding module configured to encode the developer contact tag; a tagging module configured to automatically tag the modified lines of source code with the encoded developer contact tag associated with the developer, the modified lines of source code tagged such that the developer contact tag is available in a debugging information of executable code generated from the modified lines of source code, the debugging information comprising a source code line number that was last executed and/or a function that includes the line of source code that was last executed, and/or a function that will be called next; a debug module configured to provide the debugging information for the executable code, and generate a stack trace comprising; a name of the function; a location where the function was called; the line number of the source code where the failure occurred; and the developer contact tag; and determine the developer associated with the line of source code from the debug information by way of the developer contact tag, the module comprising, a decoding module configured to decode the developer contact tag; and a presentation module configured to present the debugging information on the display device, wherein the debugging information comprises text information in human readable form. - View Dependent Claims (8, 9, 10, 11, 12, 13, 14)
-
-
15. A system for identifying a software developer based on debugging information, the system comprising:
-
a processor; a memory in communication with the processor, the memory comprising; an identification module configured to identify a developer of a line of source code, the module comprising; a determination module configured to determine a developer contact tag for the developer; an encoding module configured to encode the developer contact tag; a tagging module configured to automatically tag the line of source code with the developer contact tag associated with the developer; a debug module configured to provide debugging information of executable code, the debug information comprising a source code line number that was last executed and/or the function that includes the line of source code that was last executed, and/or a function that will be called next; and
in response to a software failure, generating a stack trace comprising;the name of the function called; the location where the function was called; the line number of the source code where the failure occurred; and the developer contact tag; and determine the developer associated with the line of source code from the debug information by way of the developer contact tag, the module comprising; a decoding module configured to decode the developer contact tag associated with the line of source code; and a presentation module configured to present the debugging information, comprising text in human readable form. - View Dependent Claims (16, 17, 18, 19)
-
Specification