summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
diff options
context:
space:
mode:
authorEnrico Granata <egranata@apple.com>2016-05-05 01:47:44 +0000
committerEnrico Granata <egranata@apple.com>2016-05-05 01:47:44 +0000
commit5ee54086251b7380c2997ff090311cdb739c17ea (patch)
tree145e11ab704b7cf141508966d59fc0f2da31afe2 /lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp
parent8752be775c938cf528dd3471d69f6e36e8f6c100 (diff)
downloadbcm5719-llvm-5ee54086251b7380c2997ff090311cdb739c17ea.tar.gz
bcm5719-llvm-5ee54086251b7380c2997ff090311cdb739c17ea.zip
Allow LanguageRuntimes to return an error if they fail in the course of dynamic type discovery
This is not meant to report that a value doesn't have a dynamic type - it is only meant as a mechanism to propagate actual type discovery issues (e.g. malformed type metadata for languages that have such a notion) This information is used by ValueObjectDynamic to set its own m_error, which is a fairly sharp and heavyweight tool to begin with For the time being, this is an architectural improvement but a practical no-op as no existing runtimes are actually setting errors llvm-svn: 268591
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api/thread/main2.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud