Stream: git-wasmtime

Topic: wasmtime / issue #2379 lightbeam panicked when either run...

Wasmtime GitHub notifications bot (Sep 27 2021 at 17:30):

alexcrichton commented on issue #2379:

Lightbeam was removed in https://github.com/bytecodealliance/wasmtime/pull/3390 as explained in RFC 14, so I'm going to close this.

Wasmtime GitHub notifications bot (Sep 27 2021 at 17:30):

alexcrichton closed issue #2379:

- What are the steps to reproduce the issue?
t.wasm is wat2wasm from below text:

(module
  (func $add (param $lhs i32) (param $rhs i32) (result i32)
    get_local $lhs
    get_local $rhs
    i32.add)
  (export "add" (func $add))
)

./wasmtime run --lightbeam t.wasm 1 2
./wasmtime wasm2obj --lightbeam t.wasm t.obj
**- What do you expect to happen? What does actually happen? Does it panic, and
if so, with which assertion?**
Expect to be run without any issue. Got error with the output:

thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', /PATH/wasmtime/crates/lightbeam/src/backend.rs:637:35
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

- Which Wasmtime version / commit hash / branch are you using?
main latest by now, commit 12e658a1ef344ccacf872accb0cadd7ef6e8cf4a
- If relevant, can you include some extra information about your environment?
(Rust version, operating system, architecture...)
rustc 1.45.2, MacOS

Last updated: Nov 22 2024 at 16:03 UTC