@article {arxiv:2015:dsousa,
	title = {Preventing Atomicity Violations with Contracts},
	journal = {ArXiv e-prints},
	year = {2015},
	note = {<p>n/a</p>
},
	abstract = {<p>Software developers are expected to protect concurrent accesses to shared regions of memory with some mutual exclusion primitive that ensures atomicity properties to a sequence of program statements. This approach prevents data races but may fail to provide all necessary correctness properties.The composition of correlated atomic operations without further synchronization may cause atomicity violations. Atomic violations may be avoided by grouping the correlated atomic regions in a single larger atomic scope. Concurrent programs are particularly prone to atomicity violations when they use services provided by third party packages or modules, since the programmer may fail to identify which services are correlated. In this paper we propose to use contracts for concurrency, where the developer of a module writes a set of contract terms that specify which methods are correlated and must be executed in the same atomic scope. These contracts are then used to verify the correctness of the main program with respect to the usage of the module(s). If a contract is well defined and complete, and the main program respects it, then the program is safe from atomicity violations with respect to that module. We also propose a static analysis based methodology to verify contracts for concurrency that we applied to some real-world software packages. The bug we found in Tomcat 6.0 was immediately acknowledged and corrected by its development team.</p>
},
	keywords = {and Cluster Computing, Computer Science - Distributed, Computer Science - Programming Languages, Computer Science - Software Engineering, Parallel},
	url = {http://arxiv.org/abs/1505.02951},
	attachments = {https://docentes.fct.unl.pt/sites/default/files/joao-lourenco/files/1505.02951v1-dsousa.pdf},
	author = {Sousa, D. G. and Dias, R. J. and Ferreira, C. and Louren{\c c}o, J. M.}
}
