Wasmtime GitHub notifications bot (Jun 09 2025 at 21:45): Wasmtime GitHub notifications bot (Jun 09 2025 at 21:45):posborne requested pchickey for a review on PR #10992.
Wasmtime GitHub notifications bot (Jun 09 2025 at 21:45):posborne requested wasmtime-core-reviewers for a review on PR #10992.
Wasmtime GitHub notifications bot (Jun 09 2025 at 21:45):posborne opened PR #10992 from posborne:stack-switching-backtrace-fix to bytecodealliance:main:
A refactor during the stack switching runtime changes introduced a defect not present in the base stack switching code. The
chunksiterator call ends up skipping elements and thewindowscall would require pulling in something likeitertools::zip_longestto work, so I just restored an impl closer to the original (but with more fine-grained unsafe calls).This code has coverage but only in the final round of stack switching changes.
Original Discussion: https://github.com/bytecodealliance/wasmtime/pull/10388#discussion_r2114747895. I didn't look closely enough when I took on this approach and w/o testing this slipped through (though can't really be hit yet).
Failing Test with current main + cranelift changes + tests: https://github.com/posborne/wasmtime/actions/runs/15538863221/job/43744530801#step:19:1165
CC @frank-emrich, @dhil
<!--
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
-->
Last updated: Dec 06 2025 at 06:05 UTC