The write API is forced to ensure that the number of bytes written from the iterator matches the varnode.size provided. In the event that this does not match, in order to prevent symbolic memory corruption, the write is rolled back before an error is returned.
An unchecked version of the API could avoid the checks and the rollback mechanism by assuming the data provided matches the varnode.size.
The
write
API is forced to ensure that the number of bytes written from the iterator matches thevarnode.size
provided. In the event that this does not match, in order to prevent symbolic memory corruption, the write is rolled back before an error is returned.An unchecked version of the API could avoid the checks and the rollback mechanism by assuming the data provided matches the
varnode.size
.