8 results about "Control flow analysis" patented technology

The invention discloses a unit test coverage rate intelligent optimization method guided by using a control flow. The method comprises the following steps: S1, obtaining and preprocessing a to-be-tested code; s2, a cycle generation stage: calling a predefined tool by using a large generative model to dynamically obtain a code to be tested, and generating a unit test code; s3, repairing the unit test codes which fail to compile or run; s4, acquiring the coverage rate and coverage information of the unit test code; performing control flow analysis on the to-be-detected code according to the coverage information and the coverage rate, and outputting a control flow information set; and uncovered control flow information is fed back to the generation cycle stage as output. According to the method, the automation degree of unit test generation based on the large model is high, the effectiveness of the codes generated by the large model is effectively improved, the coverage rate of the unit test codes generated by the large model is obviously improved, and the problems that the effectiveness of the codes generated by other unit test automatic generation tools based on the large model is low and the coverage rate in a complex scene is low are solved.

The invention discloses a static analysis tool test case generation method based on a program slicing technology, which comprises the following steps: step 1) according to a defect report of a static analysis tool, collecting and extracting variable information related to generation of a specific defect in a program as a slicing criterion; 2) through control flow analysis and data flow analysis, recording data and a control dependency relationship between statements, constructing a program dependency graph, and calculating a statement set having a dependency relationship with a slicing criterion; 3) positioning nodes corresponding to the statement set in the abstract syntax tree of the source code through a depth-first search algorithm, and deleting other nodes; the method comprises the following steps of (1) collecting a user-defined type or an external function declaration which is used through static program analysis, and outputting the type definition and the function declaration to an independent header file, and (5) writing edited codes into a file, and clearing redundant information to serve as a test case, the method adopts two-section analysis, and the test case can be generated efficiently and precisely.

The application discloses a source code processing method and device and electronic equipment. The method comprises the following steps: obtaining source code and configuration information of a project; performing syntax analysis processing on the source code based on the configuration information, and generating an abstract syntax tree of the source code; determining a target node of a correlation function in the abstract syntax tree, performing analysis processing on the target node, and obtaining an analysis processing result of the target node; performing code block division based on the analysis processing result of the target node, obtaining a code block division result of the target node, performing control flow analysis based on the code block division result of the target node, and generating a control flow graph of the target node; and performing dependency analysis based on the control flow graph of the target node, and obtaining dependency information of the target node. In combination with common static code analysis technology and a dependency information extraction method, the dependency relationship of each function is extracted, code understanding and code transplantation are facilitated, and the problem of how to extract dependency information in the code when software testing is performed on the source code is solved.

The application provides an LLM+RAG-based low-code platform script generation method and system, relates to the technical field of script generation, and comprises the following steps: constructing a semantic graph by analyzing user requirements, retrieving and screening a component combination that can be connected in series, generating an original script by using a large language model, and finally generating an executable script and deploying and running the executable script through control flow analysis and variable initialization. The application realizes the automatic generation of an executable script from a natural language requirement, and improves the development efficiency and code reliability.

This invention provides a low-code platform script generation method and system based on LLM+RAG, belonging to the field of script generation technology. The method includes constructing a semantic graph by analyzing user requirements, retrieving and filtering chainable component combinations, generating a raw script using a large language model, refining it through control flow analysis and variable initialization, and finally generating an executable script for deployment and execution. This invention achieves automated generation from natural language requirements to executable scripts, improving development efficiency and code reliability.

The invention discloses a program labyrinth protection method based on jump statements and dispersed encrypted map construction, which comprises the following steps of: performing control flow analysis on an original program to generate an equivalent block, an initialization block, a redundant calculation block, an opaque predicate and an error path, and expanding a key control flow edge into a labyrinth structure comprising a plurality of correct paths and error paths. A binary maze map is generated for correct behaviors of each conditional jump intersection, and the map is fragmented, encrypted and disguised as common data to be stored dispersedly. During operation, the navigator calculates an index based on a current instruction address and a local execution context, locates and decrypts a target map fragment, and reads a map bit to control jump; meanwhile, sentinel points are arranged at key nodes of the labyrinth, a debugging environment and indexes are detected, abnormal decryption is carried out, progressive countering is triggered or an execution stream is guided to enter an error path, and therefore under the condition that the program performance is slightly influenced, the reverse and dynamic debugging resisting capacity of a program is greatly improved.

The application provides a sandbox-free environment Vue single file component development and rendering implementation method and system, relates to the technical field of component development, and comprises receiving declarative configuration data containing a component tree, attribute binding and a life cycle hook; constructing a control flow graph and inferring capability requirements through control flow analysis, generating a capability authorization matrix recording path and capability mapping, and allocating a dynamic permission token accordingly; constructing a virtualization layer with a host object image, verifying permissions and synchronizing host status through an interceptor during operation; initializing a component instance and executing a hook, establishing a responsive observation, and triggering local re-rendering when data changes; and submitting updates after performing a security scan on the re-rendered DOM to remove dangerous content. The application realizes safe and efficient component rendering and permission control in a sandbox-free environment.

An execution environment has been designed that detects likely data exfiltration by using taint tracking and abstract execution. The execution environment is instrumented to monitor for use of functions identified as having functionality for transferring data out of an execution environment. In addition, heuristics-based rules are defined to mark or “taint” objects (e.g., variables) that are likely targets for exfiltration. With taint tracking and control flow analysis, the execution environment tracks the tainted objects through multiple execution paths of a code sample. After comprehensive code coverage, logged use of the monitored functions are examined to determine whether any tainted objects were passed to the monitored functions. If so, the logged use will indicate a destination or sink for the tainted source. Each tainted source-sink association can be examined to verify whether the exfiltration was malicious.