alexcrichton opened PR #12755 from alexcrichton:fix-fuzz to bytecodealliance:main:
This commit fixes an accidental mistake from #12542 where when the
limitof stack frames for the fuzzer to capture isNonethen it meant that backtraces were never captured. This updates the assertion logic to handle a missingWasmBacktraceand the case thatstacks.limitisNone.<!--
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 wasmtime-fuzz-reviewers for a review on PR #12755.
github-actions[bot] added the label fuzzing on PR #12755.
github-actions[bot] commented on PR #12755:
Subscribe to Label Action
cc @fitzgen
<details>
This issue or pull request has been labeled: "fuzzing"Thus the following users have been cc'd because of the following labels:
- fitzgen: fuzzing
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
fitzgen submitted PR review.
fitzgen added PR #12755 Fix a stacks fuzzer regression to the merge queue.
fitzgen merged PR #12755.
fitzgen removed PR #12755 Fix a stacks fuzzer regression from the merge queue.
Last updated: Mar 23 2026 at 16:19 UTC