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.

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

Make pedantic checks in java_verify optional #41

Closed
atomb opened this issue Jul 31, 2015 · 3 comments
Closed

Make pedantic checks in java_verify optional #41

atomb opened this issue Jul 31, 2015 · 3 comments
Assignees
Labels
obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing type: enhancement Issues describing an improvement to an existing feature or capability wontfix Closed issues that we decided not to fix, but are still potentially relevant

Comments

@atomb
Copy link
Contributor

atomb commented Jul 31, 2015

When java_verify completes execution of a method, it checks the assignments and return values as specified in the JavaSetup block, but also checks that the method has not allocated any new arrays, initialized any new classes, and a number of other things. Sometimes this is desirable behavior, but other times these errors could be downgraded to warnings. We should make it possible to continue execution even if one of these checks fails.

@atomb atomb added the type: enhancement Issues describing an improvement to an existing feature or capability label Aug 5, 2015
@atomb atomb self-assigned this Oct 12, 2015
@atomb
Copy link
Contributor Author

atomb commented Oct 13, 2015

It's now possible to allow allocations with the java_allow_alloc command.

@weaversa
Copy link
Contributor

Will you provide a small example of where to use the command?

@atomb
Copy link
Contributor Author

atomb commented Oct 13, 2015

This example should cover the basic idea:

https://github.com/GaloisInc/saw-script/blob/master/examples/java/alloc.saw
https://github.com/GaloisInc/saw-script/blob/master/examples/java/Alloc.java

You can see the difference by commenting and uncommenting the java_allow_alloc line.

@atomb atomb added the obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing label Apr 2, 2019
@atomb atomb added the wontfix Closed issues that we decided not to fix, but are still potentially relevant label Jan 29, 2021
@atomb atomb closed this as completed Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing type: enhancement Issues describing an improvement to an existing feature or capability wontfix Closed issues that we decided not to fix, but are still potentially relevant
Projects
None yet
Development

No branches or pull requests

2 participants