Stream: git-wasmtime

Topic: wasmtime / PR #12929 Use traps when checking initial tabl...


view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 14:34):

alexcrichton opened PR #12929 from alexcrichton:fix-init-with-trap to bytecodealliance:main:

Instead of using a custom error string this enables fuzzing to, for example, see that a Trap was returned and consider the fuzz test case a normal failure. These code paths are only executed when bulk_memory is disabled which is pretty rare, and also explains why it's come up in fuzzing only just now after #12883.

<!--
Please make sure you include the following information:

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 14:34):

alexcrichton requested dicej for a review on PR #12929.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 14:34):

alexcrichton requested wasmtime-core-reviewers for a review on PR #12929.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 14:34):

alexcrichton added the label fuzz-bug on PR #12929.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 14:49):

dicej submitted PR review.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 14:51):

alexcrichton added PR #12929 Use traps when checking initial table/memory bounds to the merge queue.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 15:25):

alexcrichton merged PR #12929.

view this post on Zulip Wasmtime GitHub notifications bot (Apr 01 2026 at 15:25):

alexcrichton removed PR #12929 Use traps when checking initial table/memory bounds from the merge queue.


Last updated: Apr 13 2026 at 00:25 UTC