The unsound function dump_code_load_record uses from_raw_parts to directly convert
the pointer addr and len into a slice without any validation and that memory block
would be dumped.
Thus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires
the caller to guarantee that the addr is valid and len must not overflow.
Otherwise, the function could dump the memory into file illegally, causing memory leak.
Note: this is an internal-only crate in the Wasmtime project not intended for
external use and is more strongly signaled nowadays as of
bytecodealliance/wasmtime#10963.
Please open an issue in Wasmtime if you're using this crate directly.
wasmtime-jit-debug15.0.1The unsound function
dump_code_load_recordusesfrom_raw_partsto directly convertthe pointer
addrandleninto a slice without any validation and that memory blockwould be dumped.
Thus, the 'safe' function dump_code_load_record is actually 'unsafe' since it requires
the caller to guarantee that the addr is valid and len must not overflow.
Otherwise, the function could dump the memory into file illegally, causing memory leak.