Memory leak detection method based on symbolic execution

Abstract

The invention aims at overcoming the memory leak defect and providing a memory leak detection method based on symbolic execution. Firstly, tested source codes are processed by using a static analysis tool to obtain static memory leak alarms; then, the source codes and the memory leak alarms are simultaneously input into a pile inserting device to obtain pile-inserted codes; then, the pile-inserted codes are input into a test case generating module to generate a large number of test cases and execute all test cases; the target memory leak situation is reported after operation of each test case finishes, finally all test execution outputs are summarized, and memory leak testing results are judged. The memory leak detection method solves the false alarming problem of static memory leak analysis and neglected alarming problem of dynamic testing, utilizes a symbolic execution technology to generate test cases, decreases artificial verification works of static analysis of memory leak results and improves dynamic execution efficiency.

Description

technical field [0001] The invention belongs to the fields of software engineering and software testing, and in particular relates to a method for detecting software memory leaks, which mainly uses symbolic execution technology to solve the problem of false positives in static memory leak analysis and false positives in dynamic testing. Background technique [0002] In a C / C++ program, a memory leak means that the dynamically allocated memory in the program is not released for some reason, so that the system cannot allocate the memory again. There are two types of memory leaks: lost references and forgotten releases. A loss of reference refers to the loss of all pointers or references to a dynamically allocated memory object, making the memory object unreachable. Forgetting to release means that although the dynamically allocated memory is reachable by pointers or references, it is not accessed and released during the rest of the program. [0003] Static analysis of memory...

AI Technical Summary

Problems solved by technology

A large number of suspected memory leak alerts from static analysis require manual verification one by one, which is time-consuming and laborious

The method of dynamically testing memory leaks requires test case-driven testing, and no leaks can be detected without the code that the test case passes through.

And because there is no target, dynamic testing needs to insert piles for the entire tested code, and the running efficiency is not high

Images