Verifying software malfunction sources among disparate code sources
AssigneeAurora Labs Ltd.
InventorsZohar Fox, Carmit Sahar
Life of this patent
Estimating the term…
Abstract
Disclosed herein are techniques for identifying sources of software-based malfunctions. Techniques include identifying a potential software malfunction in a system, the system having multiple code sets associated with a plurality of different software sources; accessing a line-of-code behavior and relation model representing execution of functions of the code sets; identifying, based on the line-of-code behavior and relation model, a code set determined to have the potential to cause, a least in part, the potential software malfunction; and determining a source identifier of the identified code set.
Claims20
A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for identifying sources of software-based malfunctions, comprising:
- identifying a potential software malfunction in a system, the system having multiple code sets associated with (i) a plurality of different software sources and (ii) at least one controller of the system;
- accessing a line-of-code behavior and relation model representing execution of functions of the code sets, wherein the line-of-code behavior and relation model was generated dynamically based on data associated with real-time operations of the at least one controller;
- identifying, based on the line-of-code behavior and relation model, a code set from among the code sets determined to have the potential to cause, at least in part, the potential software malfunction;
- and
- determining a source identifier of the identified code set.
A computer-implemented method for identifying sources of software-based malfunctions, the method comprising:
- identifying a potential software malfunction in a system, the system having multiple code sets associated with (i) a plurality of different software sources and (ii) at least one controller of the system;
- accessing a line-of-code behavior and relation model representing execution of functions of the code sets, wherein the line-of-code behavior and relation model was generated dynamically based on data associated with real-time operations of the at least one controller;
- identifying, based on the line-of-code behavior and relation model, a code set from among the code sets determined to have caused, at least in part, the potential software malfunction;
- and
- determining a source identifier of the identified code set.
Dependencies are inferred from the claim text.