summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/python_api
diff options
context:
space:
mode:
authorZachary Turner <zturner@google.com>2015-11-02 19:19:49 +0000
committerZachary Turner <zturner@google.com>2015-11-02 19:19:49 +0000
commit7d564544eb73710e1a5769b9832890f620d0997d (patch)
treed501d44cf8dc8e550f573e2b3354a8ef3286e443 /lldb/packages/Python/lldbsuite/test/python_api
parentdcbac6285a1d72d31b842342be04410b6055aa28 (diff)
downloadbcm5719-llvm-7d564544eb73710e1a5769b9832890f620d0997d.tar.gz
bcm5719-llvm-7d564544eb73710e1a5769b9832890f620d0997d.zip
Make dosep correctly invoke the top-level script when forking out
packages/Python/lldbsuite is now a Python package, and it relies on its __init__.py being called to do package-level initialization. If you exec packages/Python/lldbsuite/dotest.py directly, you won't get this package level initialization, and things will fail. But without this patch, this is exactly what dosep itself does. To launch the multi-processing fork, it was hardcoding a path to dotest.py and exec'ing it from inside the package. The fix here is to get the path of the top-level script, and then exec'ing that instead. A more robust solution would involve refactoring the code so that dosep execs some internal script that imports lldbsuite, but that's a bit more involved. Differential Revision: http://reviews.llvm.org/D14157 Reviewed by: Todd Fiala llvm-svn: 251819
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/python_api')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud