Ammonia: an approach for deriving project-specific bug patterns

DOI DOI HANDLE PDF Web Site 参考文献47件 オープンアクセス

書誌事項

公開日
2020-03-07
資源種別
journal article
権利情報
  • https://creativecommons.org/licenses/by/4.0
  • https://creativecommons.org/licenses/by/4.0
DOI
  • 10.1007/s10664-020-09807-w
  • 10.48550/arxiv.2001.09630
公開者
Springer Science and Business Media LLC

この論文をさがす

説明

<jats:title>Abstract</jats:title><jats:p>Finding and fixing buggy code is an important and cost-intensive maintenance task, and static analysis (SA) is one of the methods developers use to perform it. SA tools warn developers about potential bugs by scanning their source code for commonly occurring bug patterns, thus giving those developers opportunities to fix the warnings (potential bugs) before they release the software. Typically, SA tools scan for general bug patterns that are common to any software project (such as null pointer dereference), and not for project specific patterns. However, past research has pointed to this lack of customizability as a severe limiting issue in SA. Accordingly, in this paper, we propose an approach called , which is based on statically analyzing changes across the development history of a project, as a means to identify project-specific bug patterns. Furthermore, the bug patterns identified by our tool do not relate to just one developer or one specific commit, they reflect the project as a whole and compliment the warnings from other SA tools that identify general bug patterns. Herein, we report on the application of our implemented tool and approach to four Java projects: , , , and . The results obtained show that our tool could detect 19 project specific bug patterns across those four projects. Next, through manual analysis, we determined that six of those change patterns were actual bugs and submitted pull requests based on those bug patterns. As a result, five of the pull requests were merged.</jats:p>

収録刊行物

参考文献 (47)*注記

もっと見る

関連プロジェクト

もっと見る

キーワード

詳細情報 詳細情報について

問題の指摘

ページトップへ