Abstract
This paper highlights the issues of detecting Java concurrency bugs using static code analysis tools. Concurrency bugs are often hard to find because of interleaving threads and there is need to use static analysis tools to detect the concurrency bugs. In the literature review, we established that there are number of static analysis tools such as FindBugs, JLint and Chord, used in experiments to determine their ability to detect the Java concurrency bugs. However, there are still tools in the class of open source static analysis that needs experimental evidence for their ability to find concurrency bugs. In this study we selected three tools CheckThread, RacerX and RELAY. The experiment and survey is used to find out the answers for formulated research questions in the introduction section.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
