diff options
| author | Enrico Granata <egranata@apple.com> | 2015-02-11 02:35:39 +0000 |
|---|---|---|
| committer | Enrico Granata <egranata@apple.com> | 2015-02-11 02:35:39 +0000 |
| commit | 560558eb7c1deee76a1adb941e001e074dba460d (patch) | |
| tree | 361a34a9afb6b9516874d4537736cae2b917806a /lldb/source/Commands/CommandObjectTarget.cpp | |
| parent | 7ad134a7467c97ce9d8ef46fea90267a03c30b30 (diff) | |
| download | llvm-560558eb7c1deee76a1adb941e001e074dba460d.zip llvm-560558eb7c1deee76a1adb941e001e074dba460d.tar.gz llvm-560558eb7c1deee76a1adb941e001e074dba460d.tar.bz2 | |
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/source/Commands/CommandObjectTarget.cpp')
| -rw-r--r-- | lldb/source/Commands/CommandObjectTarget.cpp | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/lldb/source/Commands/CommandObjectTarget.cpp b/lldb/source/Commands/CommandObjectTarget.cpp index 9188283..b9e4942 100644 --- a/lldb/source/Commands/CommandObjectTarget.cpp +++ b/lldb/source/Commands/CommandObjectTarget.cpp @@ -773,6 +773,10 @@ public: { DumpValueObjectOptions options(m_varobj_options.GetAsDumpOptions()); + if (false == valobj_sp->GetTargetSP()->GetDisplayRuntimeSupportValues() && + true == valobj_sp->IsRuntimeSupportValue()) + return; + switch (var_sp->GetScope()) { case eValueTypeVariableGlobal: |