Verifying software malfunction sources among disparate code sources

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.

1 - 20 . (canceled) 
     
     
         21 . 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 of at least one controller in a system, the system being associated with multiple code sets, the code sets having respective different source identifiers and being associated with controlling different runtime operations of the system;   generating, using static or dynamic analysis, a line-of-code behavior and relation model that is based on functional analysis of multiple datasets associated with the different runtime operations and models execution of a software package including at least one of the code sets; and   identifying, based on the line-of-code behavior and relation model, a code set from among the code sets, the identified code set being determined to have a potential to cause, at least in part, the potential software malfunction.   
     
     
         22 . The non-transitory computer-readable medium of  claim 21 , wherein the respective different source identifiers are associated with a plurality of different code set sources. 
     
     
         23 . The non-transitory computer-readable medium of  claim 22 , wherein the code sets are associated with different devices that generated the code sets. 
     
     
         24 . The non-transitory computer-readable medium of  claim 21 , wherein at least a portion of the code sets are dependent on each other, represented by at least one dependency. 
     
     
         25 . The non-transitory computer-readable medium of  claim 24 , wherein the line-of-code behavior and relation model models the at least one dependency. 
     
     
         26 . The non-transitory computer-readable medium of  claim 21 , wherein the line-of-code behavior and relation model is generated through a machine learning process. 
     
     
         27 . The non-transitory computer-readable medium of  claim 21 , wherein generating the line-of-code behavior and relation model comprises determining a sequence of functions associated with at least one segment of the software package. 
     
     
         28 . The non-transitory computer-readable medium of  claim 21 , wherein the code set is identified based on a software change associated with the at least one controller. 
     
     
         29 . The non-transitory computer-readable medium of  claim 21 , wherein the line-of-code behavior and relation model models execution of a software change. 
     
     
         30 . The non-transitory computer-readable medium of  claim 21 , wherein the line-of-code behavior and relation model was generated based on at least one function or functional relationship determined through functional analysis of at least one of the code sets. 
     
     
         31 . The non-transitory computer-readable medium of  claim 21 , wherein the operations further comprise sending a report of the potential software malfunction to a remote device. 
     
     
         32 . The non-transitory computer-readable medium of  claim 21 , wherein the operations further comprise halting an operation on the at least one controller or halting an operation on a dependent controller that is dependent on the at least one controller. 
     
     
         33 . The non-transitory computer-readable medium of  claim 21 , wherein the line-of-code behavior and relation model represents a plurality of symbols and symbol relationships. 
     
     
         34 . The non-transitory computer-readable medium of  claim 33 , wherein at least one of the symbols comprises at least one of: a variable, a buffer, a function, a call, an object, a segment of code, the at least one controller, or a functional block. 
     
     
         35 . The non-transitory computer-readable medium of  claim 33 , wherein at least one of the symbol relationships is at least one of: a dependency symbol relationship, an interdependency symbol relationship, a one-directional symbol relationship, a bi-directional symbol relationship, an iterative symbol relationship, or a recursive symbol relationship. 
     
     
         36 . A computer-implemented method for identifying sources of software-based malfunctions, the method comprising:
 identifying a potential software malfunction of at least one controller in a system, the system being associated with multiple code sets, the code sets having respective different source identifiers and being associated with controlling different runtime operations of the system;   generating, using static or dynamic analysis, a line-of-code behavior and relation model that is based on functional analysis of multiple datasets associated with the different runtime operations and models execution of a software package including at least one of the code sets; and   identifying, based on the line-of-code behavior and relation model, a code set from among the code sets, the identified code set being determined to have a potential to cause, at least in part, the potential software malfunction.   
     
     
         37 . The computer-implemented method of  claim 36 , wherein the respective different source identifiers are associated with a plurality of different code set sources. 
     
     
         38 . The computer-implemented method of  claim 36 , wherein the code set is identified based on a software change associated with the at least one controller. 
     
     
         39 . The computer-implemented method of  claim 36 , wherein the line-of-code behavior and relation model models execution of a software change. 
     
     
         40 . The computer-implemented method of  claim 36 , wherein the line-of-code behavior and relation model was generated based on at least one function or functional relationship determined through functional analysis of at least one of the code sets.