Fix step-over when SymbolContext.function is missing and symbol is present.
authorSam McCall <sam.mccall@gmail.com>
Thu, 17 Nov 2016 22:29:31 +0000 (22:29 +0000)
committerSam McCall <sam.mccall@gmail.com>
Thu, 17 Nov 2016 22:29:31 +0000 (22:29 +0000)
commit592fa122c2a2873d04cf115d9939c0d7a4f35057
tree3147862f07a5b9a9225f0336f592972ab5d857ed
parent7293f9f7cc5f0160dbb2a1fd437f0a472b735190
Fix step-over when SymbolContext.function is missing and symbol is present.

Summary:
Fix step-over when SymbolContext.function is missing and symbol is present.

With targets from our build configuration,
ThreadPlanStepOverRange::IsEquivalentContext fails to fire for relevant frames,
leading to ShouldStop() returning true prematurely.

The frame's SymbolContext, and m_addr_context have:
  - comp_unit set and matching
  - function = nullptr
  - symbol set and matching (but this is never checked)
My naive guess is that the context should be equivalent in this case :-)

Reviewers: jingham

Subscribers: lldb-commits

Differential Revision: https://reviews.llvm.org/D26804

llvm-svn: 287274
lldb/source/Target/ThreadPlanStepOverRange.cpp