Abstract

refined semantic (line 2). As described earlier, if an alarm reported at the defect detection phase is not reported by the procedure (line 3) under the abstract refined semantic with an alarm (line 5-6), we say abstractly correlates with and is denotedly correlates with and is denoted

Highlights

  • Traditional static defect detection tools can detect software defects [1 ÷ 4], e.g., null-pointer dereference (NPD), invalid arithmetic operations (IAO), and memory leak (ML), and generate independent atomic warnings automatically, but they do not take the influences among different alarms into account and identify the correlations among alarms [5]

  • The details are in the following: We provide two rigorous definitions of alarm correlation and abstract alarm correlation, and prove the soundness based on abstract interpretation

  • This paper addresses an important issue in the usability of static analysis tools: such tools tend to produce voluminous outputs and potential users are often dissuaded from using them because reviewing this output appears to be overwhelming

Read more

Summary

Introduction

Traditional static defect detection tools can detect software defects [1 ÷ 4], e.g., null-pointer dereference (NPD), invalid arithmetic operations (IAO), and memory leak (ML), and generate independent atomic warnings automatically, but they do not take the influences among different alarms into account and identify the correlations among alarms [5]. For the large newly developed software, hundreds, or even thousands of warnings are generated by tools, but generated reports are processed at a very low speed. Excessive warning generation and a large proportion of incorrect warnings may cause developers to reject the use of static analysis tools. Helping users in the alarm verification is a major challenge for current static defect detection tools [6, 7]. We explore relationships among alarms for verification, show that a correlation can exist between alarms. Once we find these groups of alarms, we only need to check whether their dominant alarm is false positive or a real defect

Objectives
Methods
Results
Conclusion

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.