DynaMine: finding common error patterns by mining software revision histories
The DOI matches its Crossref record; 1 of the 1 references it cites were found in a registry or an index.
Abstract
A great deal of attention has lately been given to addressing software bugs such as errors in operating system drivers or security bugs. However, there are many other lesser known errors specific to individual applications or APIs and these violations of application-specific coding rules are responsible for a multitude of errors. In this paper we propose DynaMine, a tool that analyzes source code check-ins to find highly correlated method calls as well as common bug fixes in order to automatically discover application-specific coding patterns. Potential patterns discovered through mining are passed to a dynamic analysis tool for validation; finally, the results of dynamic analysis are presented to the user.The combination of revision history mining and dynamic analysis techniques leveraged in DynaMine proves effective for both discovering new application-specific patterns and for finding errors when applied to very large applications with many man-years of development and debugging effort behind them. We have analyzed Eclipse and jEdit, two widely-used, mature, highly extensible applications consisting of more than 3,600,000 lines of code combined. By mining revision histories, we have discovered 56 previously unknown, highly application-specific patterns. Out of these, 21 were dynamically confirmed as very likely valid patterns and a total of 263 pattern violations were found.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
A static analyzer for large safety-critical software
Blanchet, B., Cousot, P., Cousot, R., Feret, J., Mauborgne, L., Miné, A., Monniaux, D., & Rival, X. (2003) · Proceedings of the ACM SIGPLAN 2003 conference on Programming language design and implementation · doi:10.1145/781131.781153 · Cited by 330
Research works printed but not linked: 36
- 10.5555/645920.672836 · doi:10.5555/645920.672836
- 10.1145/1040305.1040314 · DOI · Paper page
- 10.1145/503272.503275 · DOI · Paper page
- 10.5555/950792.951382 · doi:10.5555/950792.951382
- 10.5555/851042.857048 · doi:10.5555/851042.857048
- 10.1109/AERO.2005.1559604 · DOI
- D. Carlson. Eclipse Distilled. Addison-Wesley Professional 2005. D. Carlson. Eclipse Distilled. Addison-Wesley Professional 2005.
- 10.1007/11531142_23 · DOI · Paper page
- Dudney B., 2003, Wiley
- 10.5555/1251229.1251230 · doi:10.5555/1251229.1251230
- 10.1145/502034.502041 · DOI · Paper page
- 10.1109/32.908957 · DOI · Paper page
- 10.5555/950792.951355 · doi:10.5555/950792.951355
- 10.5555/850947.853338 · doi:10.5555/850947.853338
- 10.5555/942803.943741 · doi:10.5555/942803.943741
- 10.1145/512529.512539 · doi:10.1145/512529.512539
- 10.1145/988672.988679 · DOI · Paper page
- 10.1007/978-3-540-45070-2_13 · DOI
- Mannila H., 1994, Proceedings of the AAAI Workshop on Knowledge Discovery in Databases, 181
- 10.5555/519308.786921 · doi:10.5555/519308.786921
- 10.1145/337180.337200 · doi:10.1145/337180.337200
- 10.1049/ic:20040483 · DOI
- 10.1145/1007512.1007545 · doi:10.1145/1007512.1007545
- 10.1049/ic:20040475 · DOI
- Schach S. R., 2004, McGraw-Hill Science/Engineering/Math
- Shankar U., 2001, Proceedings of the 2001 Usenix Security Conference, 201
- Tate B., 2003, Manning Publications
- Wagner D., 2000, Proceedings of Network and Distributed Systems Security Symposium, 3
- 10.1007/978-3-540-31980-1_30 · DOI · Paper page
- 10.1145/566172.566212 · DOI
- 10.1109/TSE.2005.63 · DOI · Paper page
- 10.1145/1083142.1083144 · DOI
- 10.1109/TSE.2004.52 · DOI · Paper page
- 10.5555/942803.943727 · doi:10.5555/942803.943727
- 10.1049/ic:20040466 · DOI · Paper page
- 10.5555/998675.999460 · doi:10.5555/998675.999460
Cited by
The future of employment: How susceptible are jobs to computerisation?
Frey, C. B., & Osborne, M. A. (2017) · Technological Forecasting and Social Change · doi:10.1016/j.techfore.2016.08.019 · Cited by 8,727
On the naturalness of software
Hindle, A., Barr, E. T., Su, Z., Gabel, M., & Devanbu, P. (2012) · 2012 34th International Conference on Software Engineering (ICSE) · doi:10.1109/icse.2012.6227135 · Cited by 425
MAPO: Mining and Recommending API Usage Patterns
Zhong, H., Xie, T., Zhang, L., Pei, J., & Mei, H. (2009) · Lecture Notes in Computer Science · doi:10.1007/978-3-642-03013-0_15 · Cited by 410
On the naturalness of software
Hindle, A., Barr, E. T., Gabel, M., Su, Z., & Devanbu, P. (2016) · Communications of the ACM · doi:10.1145/2902362 · Cited by 307
What would other programmers do: suggesting solutions to error messages
Hartmann, B., MacDougall, D., Brandt, J., & Klemmer, S. R. (2010) · Proceedings of the SIGCHI Conference on Human Factors in Computing Systems · doi:10.1145/1753326.1753478 · Cited by 280
Metadata
- Authors
- Livshits, B., & Zimmermann, T.
- Venue
- ACM SIGSOFT Software Engineering Notes
- Published
- 2005-09
- Volume
- 30
- Issue
- 5
- Pages
- 296-305
- ISSN
- 0163-5948 (ISSN-L)
- OpenAlex
- W4254645357
- Cited by
- 96
- References
- 1
- FWCI
- 6.77
- Type
- journal article
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: DynaMine: finding common error patterns by mining software revision histories. https://app.cochat.ai/papers/10.1145/1095430.1081754
- The paper
- Livshits, B., & Zimmermann, T. (2005). DynaMine: finding common error patterns by mining software revision histories. ACM SIGSOFT Software Engineering Notes. https://doi.org/10.1145/1095430.1081754
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.