1. What contributions have the authors mentioned in the paper "Production-guided concurrency debugging" ?
The authors present Cortex: a system that helps exposing and understanding concurrency bugs that result from schedule-dependent branches, without relying on information from failing executions.
read more
2. What are the future works mentioned in the paper "Production-guided concurrency debugging" ?
In future versions, the authors plan to search for, and compare, multiple failing executions, to enrich the information provided to the programmer.
read more
![Figure 5: a) Schematic view of the program in Figure 2: boxes represent basic blocks, arrows depict conditional jumps (0 means false and 1 means true), dashed arrows depict unconditional jumps, round shapes represent program’s exit points, and [z > 0] represents a path condition; b) Per-thread symbolic traces path for three different correct production runs. T11:10 indicates that the trace for thread T1 from production run 1 has path id 10; c) Trace database, with per-thread path ids organized into prefix trees. The node label “-” indicates the root of the prefix tree. d) Production-guided schedule search employed by Cortex to find the failing schedule. SST stands for synthesized symbolic trace.](/figures/figure-5-a-schematic-view-of-the-program-in-figure-2-boxes-1euoio25.webp)
