Wasmtime GitHub notifications bot (Feb 28 2022 at 15:04): Wasmtime GitHub notifications bot (Feb 28 2022 at 15:04):alexcrichton opened issue #3858:
Discovered while debugging CI windows failures last Friday, one thing we noticed was that backtraces are, by default, not limited in Wasmtime meaning they'll capture all relevant frames. This exposed a bug in Cranelift that the unwinding information may not be correct, but at the same time it's probably not desirable to have possibly-infinitely-long stack traces in Wasmtime. Instead we should probably limit the number of frames captured in a stack trace, probably to something reasonable-ish like 100, especially since stack depth can be controlled by the guest as well.
Wasmtime GitHub notifications bot (Dec 02 2022 at 00:12):alexcrichton commented on issue #3858:
Closing in favor of https://github.com/bytecodealliance/wasmtime/issues/5052
Wasmtime GitHub notifications bot (Dec 02 2022 at 00:12):alexcrichton closed issue #3858:
Discovered while debugging CI windows failures last Friday, one thing we noticed was that backtraces are, by default, not limited in Wasmtime meaning they'll capture all relevant frames. This exposed a bug in Cranelift that the unwinding information may not be correct, but at the same time it's probably not desirable to have possibly-infinitely-long stack traces in Wasmtime. Instead we should probably limit the number of frames captured in a stack trace, probably to something reasonable-ish like 100, especially since stack depth can be controlled by the guest as well.
Last updated: Nov 22 2024 at 16:03 UTC