System for detecting interrupt-driven type program data competition

Abstract

The invention discloses a system for detecting interrupt-driven type program data competition, which comprises a front-end processor and a data race analysis engine, wherein the front-end processor comprises a disassembler, a morphology / syntax analyzer, a control flow graph constructor and a function call relation graph constructor, and the data race analysis engine comprises an interrupt priority analysis module, an interrupt state analysis module, a memory access analysis module and a race condition identifier. A static detection method is adopted in the invention, wherein a source code or assembly code is input; the detected program does not need to run; the method can be applied in the early stage of software development; the automaticity is high; and the interrupt enabled state is analyzed in iterative inter-process manner; through 'iteration', all the possible interrupt switching conditions can be extremely collected and the failed report of data race detection is reduced; and through 'inter-process', the function call and the influence of the interruption on the program state are regarded and the detection accuracy and the detection efficiency are increased.

Description

technical field [0001] The invention relates to a system for detecting data competition, in particular to a system for detecting interrupt-driven program data competition, which belongs to computer software testing and verification technology. Background technique [0002] Data race is a complex program behavior in concurrent programs, which occurs when multiple concurrent execution streams (such as threads, tasks, interrupts) simultaneously read and write the same data unit, and at least one of the operations is a write operation. Because the order between two accesses involved in data races is not determinable, the program may produce abnormal behaviors, and even lead to software or system failure in severe cases. However, data races are characterized by low probability, and often only occur under specific external environment and execution flow switching conditions, and are difficult to reproduce, and it is very difficult to debug and test them. Therefore, automatic dete...

AI Technical Summary

Problems solved by technology

[0005] (2) The interrupt-driven program is a typical embedded software, which interacts frequently with hardware and has a special operating environment. The execution state of the program is easily changed by the outside world. Therefore, it is different from traditional programs in terms of data flow analysis and other aspects.

[0006] On the other hand, due to the lack of corresponding automatic analysis tools, developers of interrupt-driven programs generally try to find data races through traditional software testing methods, that is, the way to design test cases, execute test cases, and view the running status.

This method is not very targeted, and can only rely on repeatedly executing the software and observing the running results to check whether there is a data race. Moreover, even if a problem is found in a certain test, it is difficult to reproduce; because the test cannot exhaustively In the execution state of the program, many potential data races are also missed, causing hidden dangers; in addition, the operation of embedded software depends on external devices and environments, and it is impossible to implement testing activities in the early stages of software development, resulting in data races that often only occur in the later stages. stage is discovered, at which point the cost of defect fixes is enormous

Images