Verification Witnesses from Verification Tools (SV-COMP 2024)

<h1>SV-COMP 2024</h1> <h2>Verification Witnesses</h2> <p>This file describes the contents of an archive of the 13th Competition on Software Verification (SV-COMP 2024). <a href="https://sv-comp.sosy-lab.org/2024/">https://sv-comp.sosy-lab.org/2024/</a></p> <p>The competition was organized by Dirk Beyer, LMU Munich, Germany. More information is available in the following article: Dirk Beyer. <em>State of the Art in Software Verification and Witness Validation: SV-COMP 2024.</em> In Proceedings of the 30th International Conference on Tools and Algorithms for the Construction and Analysis of Systems (TACAS 2024, Luxembourg, April 6 - 11), 2024. Springer.</p> <p>Copyright (C) Dirk Beyer <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p> <p>SPDX-License-Identifier: CC-BY-4.0 <a href="https://spdx.org/licenses/CC-BY-4.0.html">https://spdx.org/licenses/CC-BY-4.0.html</a></p> <h2>Contents</h2> <ul> <li><code>LICENSE.txt</code>: specifies the license</li> <li><code>README.txt</code>: this file</li> <li><code>witnessFileByHash/</code>: This directory contains verification witnesses. Each verification witness in this directory is stored in a file whose name is the SHA2 256-bit hash of its contents followed by the filename extension .graphml or .yml. The format of the verification witnesses is described on the format web page: <a href="https://github.com/sosy-lab/sv-witnesses/">https://github.com/sosy-lab/sv-witnesses/</a> A verification witness contains also metadata in order to relate it to the verification task for which it was produced.</li> <li><code>witnessInfoByHash/</code>: This directory contains for each verification witness in directory witnessFileByHash/ a record in JSON format (also using the SHA2 256-bit hash of the witness as filename, with .json as filename extension) that contains the meta data.</li> <li><code>witnessListByProgramHashJSON/</code>: For convenient access to all verification witnesses for a certain program, this directory represents a function that maps each program (via its SHA2256-bit hash) to a set of verification witnesses (JSON records for verification witnesses as described above) that the verification tools have produced for that program. For each program for which verification witnesses exist, the directory contains a JSON file (using the SHA2 256-bit hash of the program as filename, with .json as filename extension) that contains all JSON records for verification witnesses for that program.</li> </ul> <p>The data structure is described in the following article: Dirk Beyer. <em>A Data Set of Program Invariants and Error Paths.</em> In Proceedings of the 2019 IEEE/ACM 16th International Conference on Mining Software Repositories (MSR 2019, Montreal, Canada, May 26-27), pages 111-115, 2019. IEEE. <a href="https://doi.org/10.1109/MSR.2019.00026">https://doi.org/10.1109/MSR.2019.00026</a></p> <h2>Other Archives</h2> <p>Overview of archives from SV-COMP 2024 that are available at Zenodo:</p> <ul> <li><a href="https://doi.org/10.5281/zenodo.10669737">https://doi.org/10.5281/zenodo.10669737</a> Verification Witnesses from SV-COMP 2024 Verification Tools. Witness store (containing the generated verification witnesses)</li> <li><a href="https://doi.org/10.5281/zenodo.10669735">https://doi.org/10.5281/zenodo.10669735</a> Verifiers and Validators: FM-Tools Data Set for SV-COMP 2024. Metadata snapshot of the evaluated tools (DOIs, options, etc.)</li> <li><a href="https://doi.org/10.5281/zenodo.10669731">https://doi.org/10.5281/zenodo.10669731</a> Results of the 13th Intl. Competition on Software Verification (SV-COMP 2024). Results (XML result files, log files, file mappings, HTML tables)</li> <li><a href="https://doi.org/10.5281/zenodo.10669723">https://doi.org/10.5281/zenodo.10669723</a> SV-Benchmarks: Benchmark Set of SV-COMP 2024. Verification tasks, version svcomp24</li> <li><a href="https://doi.org/10.5281/zenodo.10671136">https://doi.org/10.5281/zenodo.10671136</a> BenchExec, version 3.21. Benchmarking framework</li> </ul> <p>All benchmarks were executed for SV-COMP 2024 <a href="https://sv-comp.sosy-lab.org/2024/">https://sv-comp.sosy-lab.org/2024/</a> by Dirk Beyer, LMU Munich, based on the following components:</p> <ul> <li><a href="https://gitlab.com/sosy-lab/benchmarking/sv-benchmarks">https://gitlab.com/sosy-lab/benchmarking/sv-benchmarks</a> svcomp24</li> <li><a href="https://gitlab.com/sosy-lab/sv-comp/bench-defs">https://gitlab.com/sosy-lab/sv-comp/bench-defs</a> svcomp24</li> <li><a href="https://github.com/sosy-lab/benchexec">https://github.com/sosy-lab/benchexec</a> 3.21</li> <li><a href="https://gitlab.com/sosy-lab/benchmarking/fm-tools">https://gitlab.com/sosy-lab/benchmarking/fm-tools</a> svcomp24</li> <li><a href="https://gitlab.com/sosy-lab/benchmarking/sv-witnesses">https://gitlab.com/sosy-lab/benchmarking/sv-witnesses</a> svcomp24</li> <li><a href="https://gitlab.com/sosy-lab/software/coveriteam">https://gitlab.com/sosy-lab/software/coveriteam</a> 1.1</li> <li><a href="https://gitlab.com/sosy-lab/benchmarking/competition-scripts">https://gitlab.com/sosy-lab/benchmarking/competition-scripts</a> svcomp24</li> </ul> <h2>Contact</h2> <p>Feel free to contact me in case of questions: <a href="https://www.sosy-lab.org/people/beyer/">https://www.sosy-lab.org/people/beyer/</a></p>