Closed davidchisnall closed 7 months ago
(Rebased, now applies cleanly)
The change makes sense, but it doesn't look like this PR changes native-vm/microvium.c
which is the source of truth for the source code. The other microvium.c
files are derived files that are generated during the build process.
I also didn't change that file in #78. I guess I need to apply the same change from that as well?
I've pushed an update that hopefully fixes it for the previous commit as well.
Yeah, looks good. Sorry, I should have caught that in the other PR as well.
On a CHERI system, the pointers into the Microvium heap give full read-write access to the entire heap. This means that bounds errors (or passing string pointers to functions that try to mutate their arguments) will corrupt VM state.
The two hooks are:
Both of these default to doing nothing, but no CHERI platforms they can be a csetbounds / candperms instruction.