summaryrefslogtreecommitdiffstats
path: root/lldb/source/Target/ThreadPlanStepRange.cpp
diff options
context:
space:
mode:
authorJason Molenda <jmolenda@apple.com>2015-12-15 00:40:30 +0000
committerJason Molenda <jmolenda@apple.com>2015-12-15 00:40:30 +0000
commit25d5b10b229d807b56c47f63809137d737d8c52f (patch)
treef55aace3963d966dd231128dbff8a950f9fd82ba /lldb/source/Target/ThreadPlanStepRange.cpp
parentef0ef2860df2bdc8de10aa4f485a6541ef5cf87f (diff)
downloadbcm5719-llvm-25d5b10b229d807b56c47f63809137d737d8c52f.tar.gz
bcm5719-llvm-25d5b10b229d807b56c47f63809137d737d8c52f.zip
When constructing an address range to "step" or "next" through,
find the largest address range (possibly combining multiple LineEntry's for this line number) that is contiguous. This allows lldb's fast-step stepping algorithm to potentially run for a longer address range than if we have to stop at every LineEntry indicating a subexpression in the source line. http://reviews.llvm.org/D15407 <rdar://problem/23270882> llvm-svn: 255590
Diffstat (limited to 'lldb/source/Target/ThreadPlanStepRange.cpp')
-rw-r--r--lldb/source/Target/ThreadPlanStepRange.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/lldb/source/Target/ThreadPlanStepRange.cpp b/lldb/source/Target/ThreadPlanStepRange.cpp
index 44c990a6130..9bddef3c65a 100644
--- a/lldb/source/Target/ThreadPlanStepRange.cpp
+++ b/lldb/source/Target/ThreadPlanStepRange.cpp
@@ -162,7 +162,7 @@ ThreadPlanStepRange::InRange ()
if (m_addr_context.line_entry.line == new_context.line_entry.line)
{
m_addr_context = new_context;
- AddRange(m_addr_context.line_entry.range);
+ AddRange(m_addr_context.line_entry.GetSameLineContiguousAddressRange());
ret_value = true;
if (log)
{
@@ -181,7 +181,7 @@ ThreadPlanStepRange::InRange ()
{
new_context.line_entry.line = m_addr_context.line_entry.line;
m_addr_context = new_context;
- AddRange(m_addr_context.line_entry.range);
+ AddRange(m_addr_context.line_entry.GetSameLineContiguousAddressRange());
ret_value = true;
if (log)
{
OpenPOWER on IntegriCloud