fix(explorer): no more 'None' assignments crashing the executor in annotation mode - #38
Merged
Merged
Conversation
…tDriver When Z3's model omits a symbolic input (unconstrained on the solved path; its int bounds arrive as literal "(assert true)"), the annotation driver serialized "-Dswat.assignment.X=None", crashing the executor in the next round with NumberFormatException: For input string: "None". Register the branch inputs with their real DSE indices and keep the concrete value recorded in the trace as fallback, mirroring svcomp/SymbolicStorage. Also skip emitting an assignment when no value is known at all, so the executor keeps the target's original value instead of parsing garbage. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Mirrors the SV-Comp symbolic storage mechanism to register the full inputs to the TargetDriver s.t. inputs for non solved vars are correctly retrieved