Debugging software failures in deployed systems is important because they impact real
users and customers. However, debugging such failures is notoriously hard in practice …

Developers spend a lot of time searching for the root causes of software failures. For this,
they traditionally try to reproduce those failures, but unfortunately many failures are so hard …

Reproducing production failures is crucial for software reliability. Alas, existing bug
reproduction approaches are not suitable for production systems because they are not …

Concurrent code is becoming increasingly important with the advent of multi-cores, but
testing concurrent code is challenging. Researchers are developing new testing techniques …

Diagnosing concurrency bugs---the process of understanding the root causes of
concurrency failures---is hard. Developers depend on reproducing concurrency bugs to …

Developers are turning to heterogeneous computing devices, such as Field Programmable
Gate Arrays (FPGAs), to accelerate data center and cloud computing workloads. FPGAs …

There has been significant interest in hardware-assisted deterministic Record and Replay
(RnR) systems for multithreaded programs on multiprocessors. However, no proposal has …

Debugging a failure usually requires reproducing it first. This can be hard for failures in
production distributed systems, where bugs are exposed only by some unusual faulty …

Hardware-assisted Record and Deterministic Replay (RnR) of programs has been proposed
as a primitive for debugging hard-to-repeat software bugs. However, simply providing …

Failure diagnosis in practical systems is difficult, and the main obstacle is that the
information a developer has access to is limited. This information is usually not enough to …