aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
diff options
context:
space:
mode:
authorbarsolo2000 <barsolo@meta.com>2025-11-03 17:22:35 -0800
committerGitHub <noreply@github.com>2025-11-03 19:22:35 -0600
commit02d93f7abbd555d93eae94c670fa0aba95758f00 (patch)
tree19b99e0f0cabddd26e248ae726af2a4985d3b661 /lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h
parentf7fff18ad09680056f028a99a961d4120063c55b (diff)
downloadllvm-02d93f7abbd555d93eae94c670fa0aba95758f00.zip
llvm-02d93f7abbd555d93eae94c670fa0aba95758f00.tar.gz
llvm-02d93f7abbd555d93eae94c670fa0aba95758f00.tar.bz2
[RISCV] Adding `vlenb` register as callee register (#165796)
In recent debug sessions we noticed that GDB debugger is showing more stack trace than lldb. After enabling unwinding log, it seems like the issue is that the CFA is dependent on the value of vlenb. vlenb doesn't change in runtime so we can assume its value from frame 0. Co-authored-by: Bar Soloveychik <barsolo@fb.com>
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/ScriptInterpreterPythonImpl.h')
0 files changed, 0 insertions, 0 deletions