Stream: git-wasmtime

Topic: wasmtime / Issue #150 Wasm file traps with wasmtime

Wasmtime GitHub notifications bot (Jul 23 2020 at 20:59):

alexcrichton commented on Issue #150:

I've run across this issue and it's pretty old at this point and we've had a lot of changes in the meantime. I've tried reproducing this but so much has changed I'm getting lots of various kinds of errors. In any case today I can't quite see any form of corruption still around, so I'm going to close. If this crops up again we can certainly reopen though!

Wasmtime GitHub notifications bot (Jul 23 2020 at 20:59):

alexcrichton closed Issue #150:

rustc_binary-wasmtime-149-repro.wasm.zip Edit: expected this issue to be number 149

This needs a nightly compiler, the miri component installed, the x86_64-unknown-linux-gnu target installed and having ran cargo miri setup. MIRI_SYSROOT refers to the path cargo miri setup eventually emits.

$ echo 'fn main() { println!("Hello world!"); }' > example.rs
$ wasmtime -g --dir . --dir $MIRI_SYSROOT rustc_binary.wasm -- example.rs --sysroot $MIRI_SYSROOT -Zcodegen-backend=metadata_only --target x86_64-unknown-linux-gnu
[...]
[2019-05-15T17:52:51Z INFO  rustc_mir::interpret::step] // bb1
[2019-05-15T17:52:51Z INFO  rustc_mir::interpret::step] StorageDead(_5)
[2019-05-15T17:52:51Z INFO  rustc_mir::interpret::step] _0 = const std::vec::SpecExtend::spec_extend(move _3, move _4) -> bb2
error while processing main module ../../target/wasm32-wasi/release/rustc_binary.wasm: Instantiation error: Trap occurred while invoking start function: wasm trap at 0x7fbd698e38df

When using wasmer with the singlepass backend it doesn't trap. (You need to build the fix/wasi_path_filestat_get branch of wasmer to fix a wasi compat problem)

Wasmtime GitHub notifications bot (Jul 31 2020 at 16:15):

bjorn3 commented on Issue #150:

I rebuilt rustc_binary.wasm yesterday. It worked perfectly.

Last updated: Nov 22 2024 at 16:03 UTC