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
Trapwas returned and consider the fuzz test case a normal failure. These code paths are only executed whenbulk_memoryis 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:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
alexcrichton requested dicej for a review on PR #12929.
alexcrichton requested wasmtime-core-reviewers for a review on PR #12929.
alexcrichton added the label fuzz-bug on PR #12929.
dicej submitted PR review.
alexcrichton added PR #12929 Use traps when checking initial table/memory bounds to the merge queue.
alexcrichton merged PR #12929.
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