Repository navigation
Emit YAML violation witnesses (format 2.3) - #1
Merged
Merged
Conversation
SV-COMP 2027 requires Java violation witnesses in the YAML format,
version 2.3. WitnessCreator now writes witness.yml with one
violation_sequence: a function_return waypoint per recorded
Verifier.nondet*() value (constraint `\result == <java literal>`,
location at the closing parenthesis of the call) and a final target
waypoint at the violating statement. witness.graphml is still written
for the validators that consume the legacy format.
- New marker fields from the executor: call index on the line, type
descriptor and source file (legacy 4-field markers still parse);
new [WITNESS_TARGET] marker carrying the uncaught throwable's stack
trace, resolved to the innermost frame inside the task sources.
- Columns come from the sources: closing `)` of the n-th nondet call
on the line, `assert`/`throw`/first token of the target statement.
- Literals per type: L suffix only when needed, char literals, f
suffix for floats, NaN/Infinity via Float/Double, strings via
`\result.equals("...")` with Java escaping.
- CLI: --input (inputs as given, listed with sha256 hashes),
--property (specification), --out, --producer-version; the legacy
positional form keeps working. Templates are found next to the jar.
- JUnit tests for literals, markers, source resolution and the writer.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds YAML violation witnesses (format 2.3), required for Java in SV-COMP 2027 (benchmarks).
witness.graphmlis still written. Refs SWAT-project/SWAT#45.Format
violation_sequenceentry:format_version: "2.3",language: Java,input_file_hashes(sha256 of the inputs as given), specification from the.prp, nodata_modelfunction_returnwaypoint perVerifier.nondet*()value: location = closing)of the call, constraint\result == <literal>(java_expression)targetwaypoint at the violating statement (assert/throw/ first token), from the innermost stack frame inside the task sourcesDetails
[WITNESS_TARGET]marker with the throwable's stack trace.Lonly when outside int range, char literals,ffor floats,Float.isNaN(\result)/\result == Double.POSITIVE_INFINITY,-0.0preserved,\result.equals("…")with Java escaping--input,--property,--out,--producer-version; legacy positional form still works. Templates are resolved next to the jar.Testing
function_return)Release
After merge: tag
v0.2.0; SWAT bumpsWITNESS_CREATOR_VERSION/SHA256(SWAT-project/SWAT draft PR). The release layout is unchanged.🤖 Generated with Claude Code