# Understanding Counterexamples for Relational Properties with DIbugger

**Authors:** Mihai Herda (Karlsruhe Institute of Technology (KIT)), Michael Kirsten, (Karlsruhe Institute of Technology (KIT)), Etienne Brunner (Karlsruhe, Institute of Technology (KIT)), Joana Plewnia (Karlsruhe Institute of, Technology (KIT)), Ulla Scheler (Karlsruhe Institute of Technology (KIT)),, Chiara Staudenmaier (Karlsruhe Institute of Technology (KIT)), Benedikt, Wagner (Karlsruhe Institute of Technology (KIT)), Pascal Zwick (Karlsruhe, Institute of Technology (KIT)), Bernhard Beckert (Karlsruhe Institute of, Technology (KIT))

arXiv: 1907.03996 · 2019-07-10

## TL;DR

This paper introduces DIbugger, a tool that helps analyze counterexamples in software verification, especially for relational properties, by enabling simultaneous debugging of related program runs to clarify property violations.

## Contribution

The paper presents DIbugger, a novel debugging tool that enhances understanding of counterexamples for relational properties in software verification.

## Key findings

- DIbugger effectively clarifies why counterexamples violate properties.
- It supports debugging multiple related programs simultaneously.
- The tool improves the verification debugging process.

## Abstract

Software verification is a tedious process that involves the analysis of multiple failed verification attempts, and adjustments of the program or specification. This is especially the case for complex requirements, e.g., regarding security or fairness, when one needs to compare multiple related runs of the same software. Verification tools often provide counterexamples consisting of program inputs when a proof attempt fails, however it is often not clear why the reported counterexample leads to a violation of the checked property. In this paper, we enhance this aspect of the software verification process by providing DIbugger, a tool for analyzing counterexamples of relational properties, allowing the user to debug multiple related programs simultaneously.

## Full text

_Full body text omitted from this summary view._ Fetch the complete paper as Markdown: https://tomesphere.com/paper/1907.03996/full.md

## Figures

2 figures with captions in the complete paper: https://tomesphere.com/paper/1907.03996/full.md

## References

14 references — full list in the complete paper: https://tomesphere.com/paper/1907.03996/full.md

---
Source: https://tomesphere.com/paper/1907.03996