aboutsummaryrefslogtreecommitdiff
path: root/clang/lib/Frontend/CompilerInvocation.cpp
diff options
context:
space:
mode:
authorFred Riss <friss@apple.com>2020-01-20 08:39:25 -0800
committerFred Riss <friss@apple.com>2020-01-21 13:35:55 -0800
commit0478eadf73c191199cba12c85785cfafb8bfa174 (patch)
tree12c4b5047f9d49d9bc9423814cd43a6940ad11c6 /clang/lib/Frontend/CompilerInvocation.cpp
parentfd109308a7b71c009402b16c5e583ee462bfe9bd (diff)
downloadllvm-0478eadf73c191199cba12c85785cfafb8bfa174.zip
llvm-0478eadf73c191199cba12c85785cfafb8bfa174.tar.gz
llvm-0478eadf73c191199cba12c85785cfafb8bfa174.tar.bz2
[lldb/DataFormatters] Fix the `$$deference$$` synthetic child
Summary: The ValueObject code checks for a special `$$dereference$$` synthetic child to allow formatter providers to implement a natural dereferencing behavior in `frame variable` for objects like smart pointers. This support was broken when used directly throught the Python API and not trhough `frame variable`. The reason is that SBFrame.FindVariable() will return by default the synthetic variable if it exists, while `frame variable` will not do this eagerly. The code in `ValueObject::Dereference()` accounted for the latter but not for the former. The fix is trivial. The test change includes additional covergage for the already-working bahevior as it wasn't covered by the testsuite before. This commit also adds a short piece of documentatione explaining that it is possible (even advisable) to provide this synthetic child outstide of the range of the normal children. Reviewers: jingham Subscribers: lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D73053
Diffstat (limited to 'clang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions