Detecting defects in Erlang programs using static analysis

Sagonas, K

dc.contributor.author	Sagonas, K	en
dc.date.accessioned	2014-03-01T02:44:34Z
dc.date.available	2014-03-01T02:44:34Z
dc.date.issued	2007	en
dc.identifier.uri	https://dspace.lib.ntua.gr/xmlui/handle/123456789/31879
dc.subject	Language	en
dc.subject	Reliability	en
dc.subject	Security	en
dc.subject	Verification	en
dc.subject.other	Computer programming languages	en
dc.subject.other	Reliability theory	en
dc.subject.other	Security of data	en
dc.subject.other	User interfaces	en
dc.subject.other	Verification	en
dc.subject.other	Erlang codes	en
dc.subject.other	Open Telecom Platform	en
dc.subject.other	Computer aided software engineering	en
dc.title	Detecting defects in Erlang programs using static analysis	en
heal.type	conferenceItem	en
heal.identifier.primary	10.1145/1273920.1273926	en
heal.identifier.secondary	http://dx.doi.org/10.1145/1273920.1273926	en
heal.publicationDate	2007	en
heal.abstract	This talk will review the main techniques used in the Dialyzer (Discrepancy AnaLYZer of ERlang programs) defect detection tool. Dialyzer employs various forms of static program analysis to automatically identify software errors in large applications written in Erlang, a concurrent functional language developed by Ericsson and commonly used for developing telecommunications software. Dialyzer is completely automatic, relatively fast, requires no annotations from its user to detect defects, and is exceptional in that it does not report any false positives. The heart of Dialyzer's analysis is inter-modular inference of success typings for Erlang functions and the talk will explain what success typings are and how they differ from type inference in statically typed language. Dialyzer, which nowadays is part of the Erlang/OTP (Open Telecom Platform) system, has been applied to large code bases of Erlang code and has identified a significant number of software defects that have remained unnoticed after years of extensive testing. The talk will also describe experiences and main lessons learned from Dialyzer's development and from feedback from its user community.	en
heal.journalName	PPDP'07: Proceedings of the 9th International ACM SIGPLAN Conference on Principles and Practice of Declarative Programming	en
dc.identifier.doi	10.1145/1273920.1273926	en
dc.identifier.spage	37	en