[Lldb-commits] [lldb] 3280292 - [lldb] Don't scan more than 10MB of assembly insns (#105890)
via lldb-commits
lldb-commits at lists.llvm.org
Tue Aug 27 14:50:49 PDT 2024
Author: Jason Molenda
Date: 2024-08-27T14:50:46-07:00
New Revision: 328029242136950204ce8bf953eb592bff946d30
URL: https://github.com/llvm/llvm-project/commit/328029242136950204ce8bf953eb592bff946d30
DIFF: https://github.com/llvm/llvm-project/commit/328029242136950204ce8bf953eb592bff946d30.diff
LOG: [lldb] Don't scan more than 10MB of assembly insns (#105890)
For supported architectures, lldb will do a static scan of the assembly
instructions of a function to detect stack/frame pointer changes,
register stores and loads, so we can retrieve register values for the
caller stack frames. We trust that the function address range reflects
the actual function range, but in a stripped binary or other unusual
environment, we can end up scanning all of the text as a single
"function" which is (1) incorrect and useless, but more importantly (2)
slow.
Cap the max size we will profile to 10MB of instructions. There will
surely be functions longer than this with no unwind info, and we will
miss the final epilogue or mid-function epilogues past the first 10MB,
but I think this will be unusual, and the failure more to missing the
epilogue is that the user will need to step out an extra time or two as
the StackID is not correctly calculated mid-epilogue. I think this is a
good tradeoff of behaviors.
rdar://134391577
Added:
Modified:
lldb/source/Symbol/FuncUnwinders.cpp
Removed:
################################################################################
diff --git a/lldb/source/Symbol/FuncUnwinders.cpp b/lldb/source/Symbol/FuncUnwinders.cpp
index d67c0a828eb350..228d9a1072deca 100644
--- a/lldb/source/Symbol/FuncUnwinders.cpp
+++ b/lldb/source/Symbol/FuncUnwinders.cpp
@@ -334,12 +334,22 @@ UnwindPlanSP FuncUnwinders::GetAssemblyUnwindPlan(Target &target,
m_tried_unwind_plan_assembly = true;
+ // Don't analyze more than 10 megabytes of instructions,
+ // if a function is legitimately larger than that, we'll
+ // miss the epilogue instructions, but guard against a
+ // bogusly large function and analyzing large amounts of
+ // non-instruction data.
+ AddressRange range = m_range;
+ const addr_t func_size =
+ std::min(range.GetByteSize(), (addr_t)1024 * 10 * 10);
+ range.SetByteSize(func_size);
+
UnwindAssemblySP assembly_profiler_sp(GetUnwindAssemblyProfiler(target));
if (assembly_profiler_sp) {
m_unwind_plan_assembly_sp =
std::make_shared<UnwindPlan>(lldb::eRegisterKindGeneric);
if (!assembly_profiler_sp->GetNonCallSiteUnwindPlanFromAssembly(
- m_range, thread, *m_unwind_plan_assembly_sp)) {
+ range, thread, *m_unwind_plan_assembly_sp)) {
m_unwind_plan_assembly_sp.reset();
}
}
More information about the lldb-commits
mailing list