Add option for specifying filename for reporting errors - #28
Merged
martinjonas merged 1 commit intoNov 20, 2025
Merged
Conversation
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
2 participants
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.
This is a hack to avoid reporting error locations in function models in the SV-COMP setting.
When a property violation happens in a library function that we model, we want to report the place of the function call in the original input program, rather than the location in the function model. This MR adds an option to specify the name of the file that should be considered when reporting property violations.
In general it would be better to output the whole stack-trace and let Symbiotic decide what to put in the witness (TBD after sv-comp26).