Show Me Why It's Correct: Saving 1/3 of Debugging Time in Program Repair with(…)
summary
iFix instruments code using call-graph and def‑use analysis, runs failing tests on multiple patched copies, aligns per-variable runtime values into a runtime comparison table, and clusters plus ranks patches to prioritize representatives. A VS Code extension is implemented and a 28‑participant study shows a 36% reduction in debugging time vs manual inspection (33% vs a state‑of‑the‑art baseline), 50% higher confidence vs manual (20% vs baseline), and at least a 39% improvement in ranking correct patches.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:53Patch filtering limits
- 3:54Introducing iFix
- 5:39Runtime behavior method
- 7:07Interactive exploration
- 8:30User study findings
- 11:39Patch sampling evaluation
- 12:41Q&A
related talks
26mHow to control your code
37mThe Bright Future of Debuggers: Challenges and Opportunities
30mDoes Your Code Hurt?
49mTreat Your Code as a Crime Scene
50mTest Intelligence for Architects
11mFix your hardest bugs with ease with Time Travel Debugging - Session Interview With Greg Law
01h 00mSOAP - Keynote: Formal Reasoning and the Hacker Way
05mDebugging Like House - Software Differential Diagnosis