dtolnay/watt

JIT runtime failed to initiate panic

Open

#30 opened on Nov 5, 2019

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Rust (31 forks)github user discovery
help wanted

Repository metrics

Stars
 (1,501 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Panics seem to get printed decently by the interpreted runtime, but not the JIT runtime.

To reproduce, cherry-pick 149ca1a421e461ecb1f88cb1b37fcceb9dd6b653 and then:

$ cargo build --release --target wasm32-unknown-unknown --manifest-path demo/impl/Cargo.toml && cargo run --manifest-path demo/caller/Cargo.toml

error: proc-macro derive panicked
 --> demo/caller/src/main.rs:3:10
  |
3 | #[derive(Demo)]
  |          ^^^^
  |
  = help: message: panicked at 'oh no!', src/lib.rs:5:5


$ cargo build --release --target wasm32-unknown-unknown --manifest-path demo/impl/Cargo.toml && WATT_JIT=/git/wasmtime/target/release/libwasmtime_api.so cargo run --manifest-path demo/caller/Cargo.toml

fatal runtime error: failed to initiate panic, error 5
error: could not compile `watt-demo-caller`.

Contributor guide

Research direction
Investigate the JIT runtime's panic handling mechanism by comparing how the interpreted runtime prints panics and tracing the panic initiation path in the JIT runtime.
Tech stack
rust
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustCargoGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60