summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorRaphael Isemann <teemperor@gmail.com>2019-08-26 09:20:59 +0000
committerRaphael Isemann <teemperor@gmail.com>2019-08-26 09:20:59 +0000
commitd43d912b4bf8f4886ca375225d4ebd7d512ea7cf (patch)
tree279d0884ae86374b41a10424c99eee7dfe5bd049 /lldb/packages/Python/lldbsuite/test/python_api
parent0a6000f2cbb40abd008338895a471f474347b80d (diff)
downloadbcm5719-llvm-d43d912b4bf8f4886ca375225d4ebd7d512ea7cf.tar.gz
bcm5719-llvm-d43d912b4bf8f4886ca375225d4ebd7d512ea7cf.zip
[lldb] Construct the dummy target when the first Debugger object is constructed
Summary: We should always have a dummy target, so we might as well construct it directly when we create a Debugger object. The idea is that if this patch doesn't cause any problems that we can get rid of all the logic that handles situations where we don't have a dummy target (as all that code is currently untested as there seems to be no way to have no dummy target in LLDB). Reviewers: labath, jingham Reviewed By: labath, jingham Subscribers: jingham, abidh, lldb-commits Tags: #lldb Differential Revision: https://reviews.llvm.org/D66581 llvm-svn: 369885
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud