0c99ac3d7e
* Capture a backtrace before calling wasm This helps mitigate the issue, at least locally, described in #829 and there's some more comments inline in the code as well. * Run rustfmt * Move around where the trace happens
This is the wasmtime-runtime crate, which contains wasm runtime library
support, supporting the wasm ABI used by wasmtime-environ,
wasmtime-jit, and wasmtime-obj.
This crate does not make a host vs. target distinction; it is meant to be compiled for the target.