A copy of this work was available on the public web and has been preserved in the Wayback Machine. The capture dates from 2017; you can also visit <a rel="external noopener" href="http://pages.cs.wisc.edu/~liblit/woda-2009/woda-2009.pdf">the original URL</a>. The file type is <code>application/pdf</code>.
<i title="ACM Press">
<a target="_blank" rel="noopener" href="https://fatcat.wiki/container/5ttq32n6ujhkxfb7h22ytvohp4" style="color: black;">Proceedings of the Seventh International Workshop on Dynamic Analysis - WODA '09</a>
With the widespread deployment of multi-core hardware, writing concurrent programs has become inescapable. This has made fixing concurrency bugs (or crugs) critical in modern software systems. Static analysis techniques to find crugs such as data races and atomicity violations are not scalable, while dynamic approaches incur high run-time overheads. Crugs pose a greater challenge since they manifest only under specific execution interleavings that may not arise during in-house testing. Thus<span class="external-identifiers"> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1145/2134243.2134252">doi:10.1145/2134243.2134252</a> <a target="_blank" rel="external noopener" href="https://dblp.org/rec/conf/issta/ThakurSLL09.html">dblp:conf/issta/ThakurSLL09</a> <a target="_blank" rel="external noopener" href="https://fatcat.wiki/release/r22jccgofjc4vbnvxy4adaw6zq">fatcat:r22jccgofjc4vbnvxy4adaw6zq</a> </span>
more »... e is a pressing need for a low-overhead program monitoring technique that can be used post-deployment. We present Cooperative Crug Isolation (CCI), a low-overhead instrumentation technique to isolate the root causes of crugs. CCI inserts instrumentation that records occurrences of specific thread interleavings at run-time by tracking whether successive accesses to a memory location were by the same thread or by distinct threads. The overhead of this instrumentation is kept low by using a novel cross-thread random sampling strategy. We have implemented CCI on top of the Cooperative Bug Isolation framework. CCI correctly diagnoses bugs in several nontrivial concurrent applications while incurring only 2-7% run-time overhead.
<a target="_blank" rel="noopener" href="https://web.archive.org/web/20170922025804/http://pages.cs.wisc.edu/~liblit/woda-2009/woda-2009.pdf" title="fulltext PDF download" data-goatcounter-click="serp-fulltext" data-goatcounter-title="serp-fulltext"> <button class="ui simple right pointing dropdown compact black labeled icon button serp-button"> <i class="icon ia-icon"></i> Web Archive [PDF] <div class="menu fulltext-thumbnail"> <img src="https://blobs.fatcat.wiki/thumbnail/pdf/ad/57/ad573f35431ddbb801ac2e3ed1e70651bda5027c.180px.jpg" alt="fulltext thumbnail" loading="lazy"> </div> </button> </a> <a target="_blank" rel="external noopener noreferrer" href="https://doi.org/10.1145/2134243.2134252"> <button class="ui left aligned compact blue labeled icon button serp-button"> <i class="external alternate icon"></i> acm.org </button> </a>