singlepass failed to find trap info for unreachable instruction

[nlewycky]

Describe the bug

When building with singlepass, wasmer panics when attempting to find information about the native instruction mapping to an unreachable in the wasm.

With cranelift and LLVM:

$ ~/wasmer-reborn/target/debug/wasmer run --cranelift ~/x.wat
error: failed to run `/home/nicholas/x.wat`
╰─> 1: RuntimeError: unreachable
           at <unnamed> (x.wat[0]:0x1a)
$ ~/wasmer-reborn/target/debug/wasmer run --llvm ~/x.wat
error: failed to run `/home/nicholas/x.wat`
╰─> 1: RuntimeError: unreachable
           at <unnamed> (x.wat[0]:0xffffffff)

With singlepass:

$ ~/wasmer-reborn/target/debug/wasmer run --singlepass ~/x.wat
thread 'main' panicked at 'failed to find instruction for 7f75aa0ae01e', lib/engine/src/trap/frame_info.rs:151:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Steps to reproduce

Here's x.wat:

(module
  (type (;0;) (func))
  (func (;0;) (type 0)
    unreachable)
  (start 0))

Run it with singlepass and engine-jit.

Expected behavior

A RuntimeError reporting the execution of an unreachable.

Actual behavior

A panic while looking up the trap info.

[syrusakbary]

I've just tested this and it doesn't happen in master with macos.

$ make build-wasmer-debug
$ ./target/debug/wasmer run --singlepass x.wat
error: failed to run `x.wat`
│   1: RuntimeError: unreachable
╰─> 2: unreachable

[syrusakbary]

This issue should be fixed on master. Closing