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
The decode_vmslice function is misleading. It doesn't decode anything, it is merely cloning out the VM (or error if not a in contract), and return it with whatever pos and len values that have been passed in, even if those values do not correspond to valid linear memory range. It does not perform any checks.
It is being used wrong in several places. e.g. in map_new_from_linear_memory, the len is actually the number of slices (8-bytes pos|len code), not the number of bytes.
The text was updated successfully, but these errors were encountered:
The
decode_vmslice
function is misleading. It doesn't decode anything, it is merely cloning out the VM (or error if not a in contract), and return it with whateverpos
andlen
values that have been passed in, even if those values do not correspond to valid linear memory range. It does not perform any checks.It is being used wrong in several places. e.g. in
map_new_from_linear_memory
, thelen
is actually the number of slices (8-bytespos|len
code), not the number of bytes.The text was updated successfully, but these errors were encountered: