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

Mutable vs readonly #709

Closed
weaversa opened this issue May 12, 2020 · 2 comments · Fixed by #755
Closed

Mutable vs readonly #709

weaversa opened this issue May 12, 2020 · 2 comments · Fixed by #755
Assignees
@ChrisEPhifer
Labels
subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm topics: error-messages Issues involving the messages SAW produces on error usability An issue that impedes efficient understanding and use
Milestone
0.6

Comments

@weaversa
Copy link
Contributor

weaversa commented May 12, 2020 •
edited
Loading

When I use crucible_alloc_readonly and a program tries to write to this memory region, I get a message about a memory region not being "mutable". It would be nice if saw could suggest that the memory region is marked as "readonly", then that might jog my mind to think that perhaps I'm using crucible_alloc_readonly when I should be using crucible_alloc.
@weaversa weaversa added topics: error-messages Issues involving the messages SAW produces on error subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm usability An issue that impedes efficient understanding and use labels May 12, 2020
@atomb atomb added this to the 0.6 milestone May 15, 2020
@ChrisEPhifer ChrisEPhifer mentioned this issue Jun 23, 2020
Merged
ChrisEPhifer added a commit that referenced this issue Jun 23, 2020
@ChrisEPhifer
Bumped Crucible to fix issue #709
d0a9ee6
@ChrisEPhifer ChrisEPhifer mentioned this issue Jun 23, 2020
Merged
ChrisEPhifer added a commit that referenced this issue Jun 23, 2020
@ChrisEPhifer
Merge pull request #755 from GaloisInc/bump-crucible
18c5a00 
Bumped Crucible to fix issue #709
@weaversa
Copy link
Contributor Author

@ChrisEPhifer Thank you!

@ChrisEPhifer
Copy link
Member

No problem! :)

@ChrisEPhifer ChrisEPhifer self-assigned this Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChrisEPhifer ChrisEPhifer

Labels
subsystem: crucible-llvm Issues related to LLVM bitcode verification with crucible-llvm topics: error-messages Issues involving the messages SAW produces on error usability An issue that impedes efficient understanding and use
Projects
None yet
Milestone
0.6
Development

Successfully merging a pull request may close this issue.

Bumped Crucible to fix issue #709 GaloisInc/saw-script
3 participants
@atomb @weaversa @ChrisEPhifer