Reflect changes in LLVM getTypeInfo() API

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214335 91177308-0d34-0410-b5e6-96231b3b80d8
Improve the way the ObjC data formatters fetch a valid frame to use for running expressions against

This is not bullet-proof, as you might end up running in a thread where you shouldn't, but the previous policy had the same drawback
Also, in cases where code-running formatters were being recursively applied, the previous policy caused deeper levels to fail, whereas this will at least get such scenarios to function
We might eventually want to consider disqualifying certain threads/frames for "viability", but I'd rather keep it simple until complexity is proven to be necessary



git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214337 91177308-0d34-0410-b5e6-96231b3b80d8
Revert a part of r214335 that I didn't mean to commit

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214340 91177308-0d34-0410-b5e6-96231b3b80d8
When resetting the number of children on a ValueObject, also clear the existing children. This avoids issues where dynamic types change, but children stay the same

git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@214341 91177308-0d34-0410-b5e6-96231b3b80d8