Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Give access to counterexamples from tactics in crucible_llvm_verify #365

Open
brianhuffman opened this issue Feb 6, 2019 · 2 comments
Open

Give access to counterexamples from tactics in crucible_llvm_verify #365

brianhuffman opened this issue Feb 6, 2019 · 2 comments
Labels
breaking A change that will break backward compatibility type: feature request Issues requesting a new feature or capability
Milestone
Someday

Comments

@brianhuffman
Copy link
Contributor

It would be useful to give saw-script users the ability to obtain the counterexample from a failed crucible_llvm_verify proof tactic within saw-script. For example, it would be nice to be able to apply a function to it, print it out in different ways, etc.
@brianhuffman brianhuffman added the type: enhancement Issues describing an improvement to an existing feature or capability label Feb 6, 2019
@atomb atomb added the breaking A change that will break backward compatibility label Apr 20, 2020
@brianhuffman
Copy link
Contributor Author

This would probably be most useful in conjunction with interactive proof functionality (#1200).

@sauclovian-g
Copy link
Contributor

See also #252.

@sauclovian-g sauclovian-g added type: feature request Issues requesting a new feature or capability and removed type: enhancement Issues describing an improvement to an existing feature or capability labels Oct 29, 2024
@sauclovian-g sauclovian-g added this to the Someday milestone Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
breaking A change that will break backward compatibility type: feature request Issues requesting a new feature or capability
Projects
None yet
Milestone
Someday
Development

No branches or pull requests
3 participants
@atomb @brianhuffman @sauclovian-g