summaryrefslogtreecommitdiffstats
path: root/lldb/scripts/Python/finish-swig-Python-LLDB.sh
diff options
context:
space:
mode:
authorEnrico Granata <egranata@apple.com>2015-02-11 02:35:39 +0000
committerEnrico Granata <egranata@apple.com>2015-02-11 02:35:39 +0000
commit560558eb7c1deee76a1adb941e001e074dba460d (patch)
tree361a34a9afb6b9516874d4537736cae2b917806a /lldb/scripts/Python/finish-swig-Python-LLDB.sh
parent7ad134a7467c97ce9d8ef46fea90267a03c30b30 (diff)
downloadbcm5719-llvm-560558eb7c1deee76a1adb941e001e074dba460d.tar.gz
bcm5719-llvm-560558eb7c1deee76a1adb941e001e074dba460d.zip
Introduce the notion of "runtime support values"
A runtime support value is a ValueObject whose only purpose is to support some language runtime's operation, but it does not directly provide any user-visible benefit As such, unless the user is working on the runtime support, it is mostly safe for them not to see such a value when debugging It is a language runtime's job to check whether a ValueObject is a support value, and that - in conjunction with a target setting - is used by frame variable and target variable SBFrame::GetVariables gets a new overload with yet another flag to dictate whether to return those support values to the caller - that which defaults to the setting's value rdar://problem/15539930 llvm-svn: 228791
Diffstat (limited to 'lldb/scripts/Python/finish-swig-Python-LLDB.sh')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud