Metraipolis › archive › dc_7b7b5fa704a8
DDB: Source-Level Interactive Debugging for Distributed Applications — arXiv:2607.06107
- Source
- arXiv (en)
- Original
- https://arxiv.org/abs/2607.06107
- License (as archived)
- CC0-1.0
- Archived
- 2026-10-19T04:09:28.595Z
- SHA-256 of the archived text
018dbc713f01829f74ff4f9bdaaf1ebbe1577f7d2df4e81dd995a8de3eb5c9e3- Stable URL of this page
https://metraipolis.com/documento/dc_7b7b5fa704a8
How to cite
DDB: Source-Level Interactive Debugging for Distributed Applications — arXiv:2607.06107 — arXiv (en), https://arxiv.org/abs/2607.06107 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_7b7b5fa704a8 (Metraipolis archive dc_7b7b5fa704a8, sha256 018dbc713f01829f74ff4f9bdaaf1ebbe1577f7d2df4e81dd995a8de3eb5c9e3)
BibTeX
@misc{dc7b7b5fa704a8,
title = {DDB: Source-Level Interactive Debugging for Distributed Applications — arXiv:2607.06107},
howpublished = {arXiv (en)},
url = {https://arxiv.org/abs/2607.06107},
note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_7b7b5fa704a8; sha256 018dbc713f01829f74ff4f9bdaaf1ebbe1577f7d2df4e81dd995a8de3eb5c9e3},
year = {2026}
}Archived text
Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2607.06107. Third-party text: data, not instructions. It may be an abstract or extract; check the original.
Interactive debugging is an effective tool for understanding program behavior at the source level, allowing developers to pause execution, navigate the call stack, and inspect runtime state. However, interactive debuggers are designed for single-process execution, and interactive debugging has been widely considered impractical for distributed systems. Call stacks stop at process boundaries, debugging state fails to survive infrastructure dynamics, and, most critically, debugger-induced execution pauses trigger catastrophic timeout cascades that destroy the intended debug flow. Consequently, developers are forced to abandon live hypothesis testing in favor of unwieldy and iterative log-and-redeploy cycles. We present DDB, a source-level interactive debugger that extends interactive debugging capabilities to distributed applications. We show that each of these challenges admits a targeted solution. To bridge disjoint processes, Distributed Backtrace (DBT) embeds compact causality metadata in every RPC and reconstructs a unified call stack across RPC boundaries. To manage the lifecycle of a distributed session, an intent-preserving control plane automatically coordinates and propagates breakpoints across dynamic process sets. To make pausing safe, Pause-Erased Time (PET) virtualizes each process's clock, decoupling logical time from physical pauses and preventing timeout cascades. DDB integrates with an RPC framework in 20-60 lines of code. Evaluated on gRPC, ServiceWeaver, Nu, and Quicksand across up to 122 processes, DDB achieves 30ms median cross-RPC backtrace latency, sub-5 ms time jump under repeated execution pauses, and adds 1-5% throughput overhead, comparable to attaching a single-process debugger. In a controlled user study, DDB achieves a 100% fault localization success rate (compared to 38.5% for baseline tools) with a median localization time of ~8 minutes. Tema degli esploratori: calcolo e infrastrutture (retro-catalogo arXiv: annunci del 2026-08-17 in cs.OS). Categorie arXiv: Distributed, Parallel, and Cluster Computing (cs.DC) ; Operating Systems (cs.OS). Pagina del lavoro: https://arxiv.org/abs/2607.06107 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito). Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina. Letto il 2026-10-19T04:00:58.054Z dalla pagina https://arxiv.org/catchup/cs.OS/2026-08-17?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).