[all-commits] [llvm/llvm-project] 56eb9a: [lldb] Bound a WebAssembly backtrace by the target...
Jonas Devlieghere via All-commits
all-commits at lists.llvm.org
Fri Jul 31 21:44:42 PDT 2026
Branch: refs/heads/main
Home: https://github.com/llvm/llvm-project
Commit: 56eb9ab86741206baacefb62a40c8a54b4382e91
https://github.com/llvm/llvm-project/commit/56eb9ab86741206baacefb62a40c8a54b4382e91
Author: Jonas Devlieghere <jonas at devlieghere.com>
Date: 2026-07-31 (Fri, 31 Jul 2026)
Changed paths:
M lldb/source/Plugins/Process/wasm/UnwindWasm.cpp
M lldb/source/Plugins/Process/wasm/UnwindWasm.h
M lldb/test/API/functionalities/gdb_remote_client/TestWasm.py
Log Message:
-----------
[lldb] Bound a WebAssembly backtrace by the target's maximum depth (#213397)
Only UnwindLLDB honored target.process.thread.max-backtrace-depth, so
UnwindWasm reported every frame the stub sent and a stack that recursed
without end was walked to its end.
Bound the frame count by the depth on every query rather than dropping
the frames that exceed it. A Wasm call stack arrives whole on the first
query, so a depth lowered after that has to still apply, which is when a
user reaches for it. The synthetic call frame addresses stay derived
from the whole stack, so the order of the frames does not depend on the
depth.
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list