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
WAMR allows to define a callback to be triggered whenever a memory enlarge operation happens. I miss the same behaviour with let's call them "generic exceptions" which may include from "wrong version" to "divided by cero" events.
Benefit
Main thread is aware of unexpected events in an asynchronous way
Implementation
As a first approach, replicate structures and logic related to enlarge memory exceptions—originally defined in wam_memory.c/h—within wasm_runtime_common.c/h.
Finally modify wasm_set_exception function to call the configured call back.
Alternatives
Any other approach would be more efficient and practical? Something missing or collateral impact?