summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities
diff options
context:
space:
mode:
authorPavel Labath <pavel@labath.sk>2019-02-27 14:16:48 +0000
committerPavel Labath <pavel@labath.sk>2019-02-27 14:16:48 +0000
commit11bc3f49da6c687cea018872c3890fd2237584a5 (patch)
treea7e9eecc5b6c9ab8e81f49fd8a0cac611c3876ab /lldb/packages/Python/lldbsuite/test/functionalities
parent7904231edb1889229bf12e5a64a598defff33edc (diff)
downloadbcm5719-llvm-11bc3f49da6c687cea018872c3890fd2237584a5.tar.gz
bcm5719-llvm-11bc3f49da6c687cea018872c3890fd2237584a5.zip
Insert blocks of python code with swig instead of modify-python-lldb.py
Summary: Swig is perfectly capable of inserting blocks of python code into its output (and we use those fascilities already), so there's no need for this to be done in a post-process step. lldb_iter is a general-purpose utility used from many classes, so I add it to the main swig file. The other two blocks are tied to a specific class, so I add it to the interface file of that class. Reviewers: zturner, jingham, serge-sans-paille Subscribers: jdoerfert, lldb-commits Differential Revision: https://reviews.llvm.org/D58350 llvm-svn: 354975
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud