Changes in trap.h

f820750b - Fix double read/writes on stream/future handles (#12873)

Mon, 30 Mar 2026 14:54:50 +0000

Fix double read/writes on stream/future handles (#12873)* Fix double read/writes on stream/future handlesThis should result in a first-class trap, not a bug.* Fix CI List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

da093747 - Relax panics in async/futures to traps/errors (#12688)

Mon, 02 Mar 2026 21:26:40 +0000

Relax panics in async/futures to traps/errors (#12688)* Relax panics in async/futures to traps/errorsThis commit is an admittance that I don't believe we're going to getto a point where we are confident enough in the fuzzing ofcomponent-model-async such that we could confidently say we'reexercising the vast majority of possible panics. Development ofcomponent-model-async has shown a steady trickle of panics over thecourse of the development of the feature, and this trend has beenpersistent over time as well.An attempt was made in #12119 to add a fuzzer dedicated to async eventsbut that didn't actually find anything in development and it has misseda number of panics present before and discovered after its introduction.Overall I do not know how to improve the fuzzer to the point that itwould find pretty much all of the existing async-related panics overtime.To help address this concern of the `concurrent.rs` implementation thiscommit goes through and replaces things like `unwrap()`, `assert!`,`panic!`, and `unreachable!` with an error-producing form. The benefitof this is that a bug in the implementation is less likely to result ina panic and instead just results in a non-spec-compliant trap. Thedownside of doing this though is that it can become unclear what errorsare "first class traps", or expected to be guest reachable, and whichare expected to be bugs in Wasmtime. To help address this I've performeda few refactorings here as well.* Some traps previously present as error strings are now promoted to using `Trap::Foo` instead. This has some refactoring of the Rust/C side as well to make it easier to define new variants. Tests were additionally added for any trap messages that weren't previously tested as being reachable.* A new `bail_bug!` macro was added (internally) for Wasmtime. This is coupled with a concrete `WasmtimeBug` error type (exported as `wasmtime::WasmtimeBug`). The intention is that `bail!` continues to be "here's a string and I'm a bit too lazy to make a concrete error" while `bail_bug!` indicates "this is a bug in wasmtime please report this if you see it".The rough vision is that if an error condition is reached, and the systemis not broken in such a way that panicking is required, then `bail_bug!`can be used to indicate a bug in Wasmtime as opposed to panicking. Thisreduces the real-world impact of hitting these scenarios by downgrading aCVE-worthy `panic!` into a bug-worthy non-spec-compliant trap. Not allpanics are able to be transitioned to this as some are load bearing froma safety perspective or similar (or indicate something equally broken),but the vast majority of cases are suitable for "return a trap, lockdown the store, and let destructors take care of everything else".This change additionally has resulted in API changes for `FutureReader`and `StreamReader`. For example creation of these types now returns a`Result` for when the `ResourceTable` is full, for example, instead ofpanicking.* Fix CI build* Translate `WasmtimeBug` to panics in debug mode* Review comments* Refactor some stream methods for fewer panics List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

b856261d - refactor recursive reentrance checks (#12349)

Wed, 14 Jan 2026 22:27:49 +0000

refactor recursive reentrance checks (#12349)* refactor recursive reentrance checksThis commit makes a few changes related to recursive reentrance checks, instancepoisoning, etc.:- Implements the more restrictive lift/lower rules described in https://github.com/WebAssembly/component-model/pull/589 such that a component instance may not lower a function lifted by one of its ancestors, nor vice-versa. Any such lower will result in a fused adapter which traps unconditionally, preventing guest-to-guest recursive reentrance without requiring data flow analysis. - Note that this required updating several WAST tests which were violating the new rule, including some in the `tests/component-model` Git submodule, which I've updated. - This is handled entirely in the `fact` module now; I've removed the `AlwaysTrap` case previously handled by `wasmtime-cranelift`.- Removes `FLAG_MAY_ENTER` from `InstanceFlags`. It is no longer needed for guest-to-guest calls due to the above, and for guest-to-host-to-guest calls we can rely on either `FLAG_NEEDS_POST_RETURN` for sync-lifted functions or the `GuestTask` call stack for async-lifted functions.- Adds a `StoreOpaque::trapped` field which is set when _any_ instance belonging to that store traps, at which point the entire store is considered poisoned, meaning no instance belonging to it may be entered. This prevents indeterminant concurrent task state left over from the trapping instance from leaking into other instances.Note that this does _not_ include code to push and pop `GuestTask` instances forguest-to-guest sync-to-sync calls, nor for host-to-guest calls using e.g. thesynchronous `Func::call` API, so certain intrinsics which expect a `GuestTask`to be present such as `backpressure.inc` will still fail in such cases. I'lladdress that in a later PR.Also note that I made a small change to `wasmtime-wit-bindgen`, adding a `Send`bound on the `T` type parameter for `store | async` functions. This allowed meto recursively call `{Typed}Func::call_concurrent` from inside a host function,and it doesn't have any downsides AFAICT.Fixes #12128* bless bindgen expansions* bless disas tests* address review feedback* sync `trap.h` with `trap_encoding.rs`...and add const assertions to `trap.rs` to help avoid future divergence. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

23e27bad - c-api: new wasmtime_trap_new_code function (#10765)

Thu, 15 May 2025 05:56:59 +0000

c-api: new wasmtime_trap_new_code function (#10765)* c-api: new wasmtime_trap_new_code function* review comments* remove accidental include List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

f8fee938 - add clang format (#7601)

Wed, 29 Nov 2023 18:39:04 +0000

add clang format (#7601)* add clang-formatWe chose WebKit style because out of all the builtin styles it seems theclosest to what already exists in wasmtime.Signed-off-by: Tyler Rockwood * c-api: don't reorder headersThe order here mattersSigned-off-by: Tyler Rockwood * c-api: apply clang-formatSigned-off-by: Tyler Rockwood * fiber: apply clang-formatSigned-off-by: Tyler Rockwood * runtime: apply clang-formatSigned-off-by: Tyler Rockwood * examples: apply clang formatSigned-off-by: Tyler Rockwood * tests: apply clang-formatSigned-off-by: Tyler Rockwood * ci: add clang-format checksSigned-off-by: Tyler Rockwood * clang-format: keep braces on the same lineThis is more the existing styleSigned-off-by: Tyler Rockwood * remove clang-formatJust use the tool defaults (LLVM)Signed-off-by: Tyler Rockwood * Fix ci nameSigned-off-by: Tyler Rockwood * manually reformat a couple of commentsprtest:fullSigned-off-by: Tyler Rockwood * disable formatting for doc-wasm.hSigned-off-by: Tyler Rockwood * manually reformat wasmtime.hSigned-off-by: Tyler Rockwood * disable formattingTo prevent a link from being brokenSigned-off-by: Tyler Rockwood * examples: fixing build commandsSigned-off-by: Tyler Rockwood * fix parameter commentSigned-off-by: Tyler Rockwood ---------Signed-off-by: Tyler Rockwood List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

42e88c7b - Fix `OutOfFuel` trap code not represented in the C API. (#5230)

Thu, 10 Nov 2022 20:42:26 +0000

Fix `OutOfFuel` trap code not represented in the C API. (#5230)This commit adds the missing "out of fuel" trap code to the C API. Without this, calls to `wasmtime_trap_code` will trigger an unreachable panic on traps from running out of fuel. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

b07b0676 - Update how exits are modeled in the C API (#5215)

Mon, 07 Nov 2022 17:35:49 +0000

Update how exits are modeled in the C API (#5215)Previously extracting an exit code was only possibly on a `wasm_trap_t` which will never successfully have an exit code on it, so the exit code extractor is moved over to `wasmtime_error_t`. Additionally extracting a wasm trace from a `wasmtime_error_t` is added since traces happen on both traps and errors now. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

f3b80ece - c-api: add wasmtime_trap_code (#3086)

Thu, 15 Jul 2021 15:31:03 +0000

c-api: add wasmtime_trap_code (#3086)Eventually this should be added to the wasmtime-go binding, addressing https://github.com/bytecodealliance/wasmtime-go/issues/63. Added a snippet to examples/interrupt.c to verify that this works as expected in manual testing. Signed-off-by: Stephan Renatus List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h

7a1b7cdf - Implement RFC 11: Redesigning Wasmtime's APIs (#2897)

Thu, 03 Jun 2021 14:10:53 +0000

Implement RFC 11: Redesigning Wasmtime's APIs (#2897)Implement Wasmtime's new API as designed by RFC 11. This is quite a large commit which has had lots of discussion externally, so for more information it's best to read the RFC thread and the PR thread. List of files: /wasmtime-44.0.1/crates/c-api/include/wasmtime/trap.h