aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Basic/Module.cpp
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2020-06-23 15:40:36 +0200
committerPavel Labath <pavel@labath.sk>2020-06-26 11:46:47 +0200
commit5ed8765e2f007e56a34e3aa0ab01f65c5aaa7e27 (patch)
tree7d2df0e57aa6e5cd19ed626eb2b7578f61be2bfa /clang/lib/Basic/Module.cpp
parentce275d3030a9dfcf9c55c81b88ae1b2c88f1828f (diff)
downloadllvm-5ed8765e2f007e56a34e3aa0ab01f65c5aaa7e27.zip
llvm-5ed8765e2f007e56a34e3aa0ab01f65c5aaa7e27.tar.gz
llvm-5ed8765e2f007e56a34e3aa0ab01f65c5aaa7e27.tar.bz2
[lldb/Unwind] Use eh_frame plan directly when it doesn't need to be augmented
Summary: This fixes a bug in the logic for choosing the unwind plan. Based on the comment in UnwindAssembly-x86, the intention was that a plan which describes the function epilogue correctly does not need to be augmented (and it should be used directly). However, the way this was implemented (by returning false) meant that the higher level code (FuncUnwinders::GetEHFrameAugmentedUnwindPlan) interpreted this as a failure to produce _any_ plan and proceeded with other fallback options. The fallback usually chosed for "asynchronous" plans was the "instruction emulation" plan, which tended to fall over on certain functions with multiple epilogues (that's a separate bug). This patch simply changes the function to return true, which signals the caller that the unmodified plan is ready to be used. The attached test case demonstrates the case where we would previously fall back to the instruction emulation plan, and unwind incorrectly -- the test asserts that the "augmented" eh_frame plan is used, and that the unwind is correct. Reviewers: jasonmolenda, jankratochvil Subscribers: davide, echristo, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D82378
Diffstat (limited to 'clang/lib/Basic/Module.cpp')
0 files changed, 0 insertions, 0 deletions