- Now using the fmt subscriber for improved formatting
- Using spans on all syscalls
- Added recorded fields on the spans instead trace and debug macros
- Adding timing on all syscall
We already depend on `tempfile`, which also provides temp dir
functionality.
This gets rid of a cargo-deny error due to a race condition in
remove_dir_all, which is a dependency of the removed "tempdir" crate.
Also bumps the minimum tempfile version in Cargo.toml files to be
consistent.
* Removed choice for object-format in create-exe and create-obj commands (and related tests)
* Removed create-obj testing for Symbol object type
* Small change to have intermediary variable instead of a big Some(_)
This change adds a basic coredump generation after a WebAssembly trap
was entered. The coredump includes rudimentary stack / process debugging
information.
A new CLI argument is added to enable coredump generation:
```
wasmer --coredump-on-trap=/path/to/coredump/file module.wasm
```
See docs/en/examples-coredump.md.
Refs https://github.com/wasmerio/wasmer/issues/3578
WASIX networking will now only be enabled if the --net flag is provided.
Otherwise it would break the Wasmer sandboxing promise.
In the future we should add more advanced networking config.
(like only allow certain ports, limit dns domains, limit ip ranges, etc )
* Remove all the STDIO related methods from the WasiRuntime trait
* Remove the special-cased Stdio VirtualFile types that where needed due to
the above WasiRuntime trait integration
* Replace the WasiRuntime::{get,set}_tty methods with a dedicated optional
TtyBridge trait
* Update the Console to always require a full WasiBidirectionalPipePair
which is used for stdio
Makes the WasiState type private, and replaces it's usage with WasiEnv
where needed.
WasiState is a complex type with many implementation details, it should
not be public.
Introduces a new WasiEnvInit type that should hold all information
required for initializing an instance.
An instance can then be created with WasiEnv::instantiate().
This method takes care of all the required setup steps to properly run a
wasi(X) module.
