A Taxonomy of Concurrency Bugs in Event-Driven Programs

Tchamgoue, Guy Martin; Ha, Ok-Kyoon; Kim, Kyong Hoon; Jun, Yong-Kee

doi:10.1007/978-3-642-27207-3_48

Cited by 6 publications

(9 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There exist several survey papers on concurrent programme analysis topics other than race bug detections for multithreaded programmes. Tchamgoue et al ., surveys techniques for bug detection and debugging in event‐driven programmes and summarizes the terminologies in the techniques. Helmbold et al ., summarizes the concepts of the race bug detection techniques for parallel programmes and presents a classification with respect to the characteristics of target programme structure (e.g.…”

Section: Related Workmentioning

confidence: 99%

A survey of race bug detection techniques for multithreaded programmes

Hong

Kim

2014

Software Testing Verif & Rel

View full text Add to dashboard Cite

SummaryAs multithreaded programmes become popular to fully utilize multicore CPUs, many race bug detection techniques have been developed to find concurrency errors in multithreaded programmes effectively. Because these techniques have different views on target programme execution and detect race bugs of various types, it is difficult to characterize, compare and improve race bug detection techniques. This paper presents a formal execution model, which can uniformly represent various views of race bug detection techniques on target programme execution. Then, this paper classifies 43 race bug detection techniques according to their target race bugs. We classify race bugs on whether or not a bug violates operation block specification and/or data association specification. This survey provides researchers with a clear top‐down view of various race bug detection techniques. In addition, the concrete examples of various race bugs in this survey can help field engineers avoid race bugs in their multithreaded programmes. Copyright © 2014 John Wiley & Sons, Ltd.

show abstract

Section: Related Workmentioning

confidence: 99%

A survey of race bug detection techniques for multithreaded programmes

Hong

Kim

2014

Software Testing Verif & Rel

View full text Add to dashboard Cite

show abstract

“…The answer to this question depends on the concurrency model in which the program is written. Most existing studies about concurrency bugs focus on thread-based concurrency [6,43,10,39,56,37,1,2].…”

Section: Introductionmentioning

confidence: 99%

A Study of Concurrency Bugs and Advanced Development Support for Actor-based Programs

Lopez

Marr

Boix

et al. 2018

Lecture Notes in Computer Science

View full text Add to dashboard Cite

The actor model is an attractive foundation for developing concurrent applications because actors are isolated concurrent entities that communicate through asynchronous messages and do not share state. Thereby, they avoid concurrency bugs such as data races, but are not immune to concurrency bugs in general. This study taxonomizes concurrency bugs in actor-based programs reported in literature. Furthermore, it analyzes the bugs to identify the patterns causing them as well as their observable behavior. Based on this taxonomy, we further analyze the literature and find that current approaches to static analysis and testing focus on communication deadlocks and message protocol violations. However, they do not provide solutions to identify livelocks and behavioral deadlocks. The insights obtained in this study can be used to improve debugging support for actor-based programs with new debugging techniques to identify the root cause of complex concurrency bugs. 1 play() -> 2 Ping = spawn(fun ping/0), 3 spawn(fun() -> pong(Ping) end). 4 5 ping() -> 6 receive 7 pong_msg -> ok 8 end. 9 10 pong(Ping) -> 11 Ping ! pong_msg, 12 receive 13 ping_msg -> ok 14 end.Listing 1.1. Communication deadlock example in Erlang (from [15]). Line 12 has a blocking receive causing the pong process to deadlock because the expected message is never sent.

show abstract

“…More bugs are generated now because today's software has become large and complex. Bug fixing is an important phase in large and complex software development [1,2]. Some bugs are critical, while others are trivial.…”

Section: Introductionmentioning

confidence: 99%

Improving predictions about bug severity by utilizing bugs classified as normal

Kusaka¹,

Dashbalbar²,

Yang³

et al. 2016

ces

View full text Add to dashboard Cite

More bugs have been generated because today's software has become large and complex. Some of these bugs are critical, while others are trivial. Because accurate prediction of bug severity enables software developers to effectively solve software problems, that accuracy aids software development and project planning. Therefore, this study presents a reliable approach to improve predictions about bug severity by utilizing bugs classified as normal, which is the default level specified in a submitted report. This approach uses attributes as well as text information in bug reports to produce more accurate prediction results. Bug reports in open source projects such as Mozilla and Eclipse were used in the experiments. The result shows that this approach performs better than other studies.

show abstract

A Taxonomy of Concurrency Bugs in Event-Driven Programs

Cited by 6 publications

References 22 publications

A survey of race bug detection techniques for multithreaded programmes

A survey of race bug detection techniques for multithreaded programmes

A Study of Concurrency Bugs and Advanced Development Support for Actor-based Programs

Improving predictions about bug severity by utilizing bugs classified as normal

Contact Info

Product

Resources

About