You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While debugging symbolic execution via Crucible is valuable in SAW, we could look at some additional integration in that context. For example, while SAW is attempting to verify a program satisfies a specification, it will often use overrides that encode the semantics of previously-verified functions to avoid having to re-analyze code.
However, it may be the case that no overrides apply, or the set of overrides that has been manually brought into scope is not exhaustive. It would be useful to have SAW drop into a debugging mode that let the user interactively examine outstanding proof obligations and have explanations for:
why the in-scope overrides cannot be used
which overrides that are not in scope might be applicable
The text was updated successfully, but these errors were encountered:
While debugging symbolic execution via Crucible is valuable in SAW, we could look at some additional integration in that context. For example, while SAW is attempting to verify a program satisfies a specification, it will often use overrides that encode the semantics of previously-verified functions to avoid having to re-analyze code.
However, it may be the case that no overrides apply, or the set of overrides that has been manually brought into scope is not exhaustive. It would be useful to have SAW drop into a debugging mode that let the user interactively examine outstanding proof obligations and have explanations for:
The text was updated successfully, but these errors were encountered: