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

Symbolic state initialization "Invalid store address" issue when using llvm_symexec #163

Closed
robby-phd opened this issue Aug 2, 2016 · 0 comments
Closed

Symbolic state initialization "Invalid store address" issue when using llvm_symexec #163

robby-phd opened this issue Aug 2, 2016 · 0 comments
Labels
obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing wontfix Closed issues that we decided not to fix, but are still potentially relevant

Comments

@robby-phd
Copy link
Contributor

The attached zip file contains an example (sha2-openbsd-llvm_symexec.saw) where llvm_symexec fails to initialize the input symbolic state with the following error message:

saw: user error ("llvm_symexec" (.../llvm-memory-model/sha2-openbsd-llvm_symexec.saw:9:15):
internal: uncaught exception: Invalid store address:  (Prelude.bvAdd
                           64
                           lss__alloc5
                           (Prelude.bvNat 64 0)))

Upon close inspection with @atomb, it is determined that the script should work.

Interestingly, another script using llvm_verify (sha2-openbsd-llvm_verify.saw) works.

llvm-memory-model.zip
@atomb atomb added obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing wontfix Closed issues that we decided not to fix, but are still potentially relevant labels Apr 2, 2019
@atomb atomb closed this as completed Apr 2, 2019
brianhuffman pushed a commit that referenced this issue Apr 26, 2021
Merge pull request #163 from GaloisInc/primitive
4ceddbd 
Replace `GlobalDef` term constructor with `Primitive`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
obsolete Issues that involve/depend on deprecated code, such that they are not worth pursuing wontfix Closed issues that we decided not to fix, but are still potentially relevant
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@atomb @robby-phd