Improving your software using static analysis to find bugs

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

Improving your software using static analysis to find bugs

Full text

Pdf (188 KB)

Source

Dynamic Languages Symposium archive
Companion to the 21st ACM SIGPLAN symposium on Object-oriented programming systems, languages, and applications table of contents

Portland, Oregon, USA

POSTER SESSION: OOPSLA posters chair's welcome table of contents

Pages: 673 - 674

Year of Publication: 2006

ISBN:1-59593-491-X

Authors

Brian Cole	University of Maryland, College Park, MD
Daniel Hakim	University of Maryland, College Park, MD
David Hovemeyer	University of Maryland, College Park, MD
Reuven Lazarus	University of Maryland, College Park, MD
William Pugh	University of Maryland, College Park, MD
Kristin Stephens	University of Maryland, College Park, MD

Sponsors

SIGPLAN: ACM Special Interest Group on Programming Languages
ACM: Association for Computing Machinery

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 12, Downloads (12 Months): 109, Citation Count: 2

Additional Information:

abstract cited by index terms collaborative colleagues

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1176617.1176667 What is a DOI?

ABSTRACT

FindBugs looks for bugs in Java programs. It is based on the concept of bug patterns. A bug pattern is a code idiom that is often an error. Bug patterns arise for a variety of reasons, such as difficult language features, misunderstood API semantics, misunderstood invariants when code is modified during maintenance, garden variety mistakes: typos, use of the wrong boolean operator and simple mistakes such as typos.FindBugs uses static analysis to inspect Java bytecode for occurrences of bug patterns. We have found that FindBugs finds real errors in most Java software. Because its analysis is sometimes imprecise, FindBugs can report false warnings, which are warnings that do not indicate true errors. In practice, the rate of false warnings reported by FindBugs is generally lower than 50%, often much lower.

CITED BY 2

	Matthew B. Dwyer , John Hatcliff , Robby Robby , Corina S. Pasareanu , Willem Visser, Formal Software Analysis Emerging Trends in Software Model Checking, 2007 Future of Software Engineering, p.120-136, May 23-25, 2007
	Jean-Baptiste Voron , Fabrice Kordon, Transforming sources to petri nets: a way to analyze execution of parallel programs, Proceedings of the 1st international conference on Simulation tools and techniques for communications, networks and systems & workshops, March 03-07, 2008, Marseille, France