Blogs (9) >>
Sun 30 October - Fri 4 November 2016 Amsterdam, Netherlands
Tue 1 Nov 2016 13:30 - 14:20 at Winterthur - Session 3 Chair(s): Michael Pradel, Omer Tripp

When a program fails, it leaves behind fragmentary clues as to what went wrong: core dumps, stack traces, log files, and so on. In this talk I describe CSI: Crash Scene Investigation, which puts these postmortem clues to work. CSI uses lightweight instrumentation and compile-time optimization to improve the quality of clues left behind in the event of a failure. After failure occurs, CSI gathers clues and performs a best-effort reconstruction of events leading up to the final, fatal blow. Our hybrid static/dynamic approach adds minimal run-time cost while providing rich, informative context in support of human debugging efforts.

Tue 1 Nov
Times are displayed in time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change

13:30 - 15:10: Session 3WODA at Winterthur
Chair(s): Michael PradelTU Darmstadt, Germany, Omer TrippIBM Research, USA
13:30 - 14:20
Best-Effort Failure Reconstruction Using CSI: Crash Scene Investigation
Ben LiblitUniversity of Wisconsin–Madison
14:20 - 15:10
What’s going on in the heap?
Sam GuyerTufts University