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

Allow pointers to one past the end of allocations #519

Merged

Conversation

langston-barrett
Copy link
Contributor

No description provided.

@langston-barrett langston-barrett changed the title Names for numbers in array length error messages Allow pointers to one past the end of allocations Aug 5, 2019
@langston-barrett langston-barrett added the subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm label Aug 5, 2019
@langston-barrett
Copy link
Contributor Author

langston-barrett commented Aug 5, 2019

I've modified this PR so that it addresses #524 as well (since that's an issue about the same bit of code). Unfortunately, I'm running into a very strange message on the example included in that issue:

[18:19:55.182] "crucible_llvm_verify" (/home/siddharthist/code/tmp/range-2/test.saw:12:1-12:21):
at /home/siddharthist/code/tmp/range-2/test.saw:12:1
could not match specified value with actual value:
  actual (simulator) value: concrete pointer: allocation = 5, offset = 10
  specified value:          concrete pointer: allocation = 5, offset = 10
  type of actual value:    i8*
  type of specified value: i8*

This looks like it is probably because of a missing case in matchArg.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants