You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From the security standpoint, it would be a benefit if we could mark some memory ranges as inaccessible (e.g. a few MB around address 0, to catch null pointer and close to null pointer access, and a few MB at the end of the stack, to catch stack overflow), failing if the VM tries to write to/read from there.
The text was updated successfully, but these errors were encountered:
From the security standpoint, it would be a benefit if we could mark some memory ranges as inaccessible (e.g. a few MB around address 0, to catch null pointer and close to null pointer access, and a few MB at the end of the stack, to catch stack overflow), failing if the VM tries to write to/read from there.
The text was updated successfully, but these errors were encountered: