Occasionally LLDB runs into contexts where the target is stopped in a C++ or Objective-C method but the "self" pointer's valid range actually doesn't cover the current location.  Before, that was confusing Clang to the point where it crashed; now, we sanity-check and fall back to pretending we're in a C function if "self" or "this" isn't available.
Occasionally LLDB runs into contexts where the
target is stopped in a C++ or Objective-C method
but the "self" pointer's valid range actually
doesn't cover the current location.  Before, that
was confusing Clang to the point where it crashed;
now, we sanity-check and fall back to pretending
we're in a C function if "self" or "this" isn't
available.


git-svn-id: 4c4cc70b1ef44ba2b7963015e681894188cea27e@143676 91177308-0d34-0410-b5e6-96231b3b80d8

apple/swift-lldb,llvm-mirror/lldb,apple/swift-lldb,apple/swift-lldb,llvm-mirror/lldb,llvm-mirror/lldb,apple/swift-lldb,apple/swift-lldb,llvm-mirror/lldb,llvm-mirror/lldb,apple/swift-lldb