Joel Dice (Dec 17 2024 at 15:10): Joel Dice (Dec 17 2024 at 15:10):You might want to look at Wizer, which instantiates a Wasm module, runs a function on that instance, captures a snapshot of the state of the instance when the function returns, and then generates a new module containing that snapshot (i.e. so the new module will effectively resume where the instance left off). However, it doesn't have any way of capturing a Wasm stack, so it can't snapshot an instance which is e.g. blocked on a host call. Not sure if there's a way to do that with Wasmtime, currently.
Anatolii Smolianinov (Dec 17 2024 at 15:39):Joel Dice said:
You might want to look at Wizer, which instantiates a Wasm module, runs a function on that instance, captures a snapshot of the state of the instance when the function returns, and then generates a new module containing that snapshot (i.e. so the new module will effectively resume where the instance left off). However, it doesn't have any way of capturing a Wasm stack, so it can't snapshot an instance which is e.g. blocked on a host call. Not sure if there's a way to do that with Wasmtime, currently.
oh thanks! right, not exactly what I want but still very useful
Notification Bot (Dec 17 2024 at 15:40):Anatolii Smolianinov has marked this topic as resolved.
Last updated: Dec 23 2024 at 13:07 UTC