Part III: Flows and Dependencies¶

In this part, we show how to follow where specific (faulty) values come from, and why they came to be.

Tracking Failure Origins shows how to instrument programs such that data flows as well as control flows and the associated dependencies are automatically tracked, allowing to easily find out where a value came from.

Creative Commons License The content of this project is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. The source code that is part of the content, as well as the source code used to format and display that content is licensed under the MIT License. Last change: 2021-02-27 17:57:06+01:00 • Cite • Imprint

How to Cite this Work

Andreas Zeller: "Part III: Flows and Dependencies". In Andreas Zeller, "The Debugging Book", https://www.debuggingbook.org/beta/html/03_Dependencies.html. Retrieved 2021-02-27 17:57:06+01:00.

@incollection{debuggingbook2021:03_Dependencies,
    author = {Andreas Zeller},
    booktitle = {The Debugging Book},
    title = {Part III: Flows and Dependencies},
    year = {2021},
    publisher = {CISPA Helmholtz Center for Information Security},
    howpublished = {\url{https://www.debuggingbook.org/beta/html/03_Dependencies.html}},
    note = {Retrieved 2021-02-27 17:57:06+01:00},
    url = {https://www.debuggingbook.org/beta/html/03_Dependencies.html},
    urldate = {2021-02-27 17:57:06+01:00}
}