Publication:
A classification of concurrency bugs in java benchmarks by developer intent

Simple item page
dc.contributor.departmentDepartment of Computer Engineering
dc.contributor.departmentDepartment of Computer Engineering
dc.contributor.departmentN/A
dc.contributor.kuauthorKeremoğlu, M. Erkan
dc.contributor.kuauthorTaşıran, Serdar
dc.contributor.kuauthorElmas, Tayfun
dc.contributor.kuprofileResearcher
dc.contributor.kuprofileFaculty Member
dc.contributor.kuprofilePhD Student
dc.contributor.otherDepartment of Computer Engineering
dc.contributor.schoolcollegeinstituteCollege of Engineering
dc.contributor.schoolcollegeinstituteCollege of Engineering
dc.contributor.schoolcollegeinstituteGraduate School of Sciences and Engineering
dc.contributor.yokidN/A
dc.contributor.yokidN/A
dc.contributor.yokidN/A
dc.date.accessioned2024-11-09T23:59:53Z
dc.date.issued2006
dc.description.abstractThis work addresses the issue of selecting the formal correctness criterion for a concurrent Java program that best corresponds to the developer's intent. We study a set of concurrency-related bugs detected in Java benchmarks reported in the literature. On these programs, we determine whether race-freedom, atomicity or refinement is the simplest and most appropriate criterion for program correctness. Our purpose is to demonstrate empirically the fact that the appropriate fix for a concurrency error and the selection of a program analysis tool for detecting such an error must be based on the proper expression of the designer's intent using a formal correctness criterion.
dc.description.indexedbyScopus
dc.description.openaccessYES
dc.description.publisherscopeInternational
dc.description.sponsoredbyTubitakEuN/A
dc.description.volume2006
dc.identifier.doi10.1145/1147403.1147407
dc.identifier.isbn978-1-59593-414-7
dc.identifier.linkhttps://www.scopus.com/inward/record.uri?eid=2-s2.0-34247546212&doi=10.1145%2f1147403.1147407&partnerID=40&md5=b2578d3d3d4ca2ad03c819f7f131d54b
dc.identifier.quartileN/A
dc.identifier.scopus2-s2.0-34247546212
dc.identifier.urihttps://research.ibm.com/haifa/Workshops/padtad2006/present/erkan_padtad.pdf
dc.identifier.urihttps://hdl.handle.net/20.500.14288/15718
dc.keywordsAtomicity
dc.keywordsConcurrency errors
dc.keywordsRace condition
dc.keywordsRefinement
dc.keywordsVerification
dc.keywordsBenchmarking
dc.keywordsError analysis
dc.keywordsHazards and race conditions
dc.keywordsJava programming language
dc.keywordsProgram compilers
dc.keywordsConcurrency errors
dc.keywordsDeveloper's intent
dc.keywordsProgram analysis tool
dc.keywordsConcurrency control
dc.languageEnglish
dc.publisherAssociation for Computing Machinery (ACM)
dc.sourceProceeding of The 2006 Workshop on Parallel and Distributed Systems: Testing and Debugging, PADTAD '06
dc.subjectJava (Computer program language)
dc.subjectCompilers (Computer programs)
dc.subjectJava
dc.subjectSoftware engineering
dc.subjectArtificial intelligence
dc.subjectComputers
dc.titleA classification of concurrency bugs in java benchmarks by developer intent
dc.typeConference proceeding
dspace.entity.typePublication
local.contributor.authoridN/A
local.contributor.authoridN/A
local.contributor.authoridN/A
local.contributor.kuauthorKeremoğlu, M. Erkan
local.contributor.kuauthorTaşıran, Serdar
local.contributor.kuauthorElmas, Tayfun
relation.isOrgUnitOfPublication89352e43-bf09-4ef4-82f6-6f9d0174ebae
relation.isOrgUnitOfPublication.latestForDiscovery89352e43-bf09-4ef4-82f6-6f9d0174ebae

Files

Collections

Publications without Fulltext