summaryrefslogtreecommitdiffstats
path: root/lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2018-06-21 13:55:19 +0000
committerPavel Labath <labath@google.com>2018-06-21 13:55:19 +0000
commit30f2e61b97effae7dade5f617482b16b778629b9 (patch)
tree54f61adefa47199579399617e57cc180399804e8 /lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h
parent4bd5c4760127319c3c1cf10c7cabc31fcd6f2246 (diff)
downloadbcm5719-llvm-30f2e61b97effae7dade5f617482b16b778629b9.tar.gz
bcm5719-llvm-30f2e61b97effae7dade5f617482b16b778629b9.zip
Disable gmodules tests on linux
These tests are extremely environment-dependent. if the environment is not module-enabled (which is the likely scenario), they won't test anything. If one happens to have a module-enabled libc++, then the he will start running into problems. The first one is that the debug info in pcm file contains relocations that ObjectFileELF doesn't handle (particularly on non-x86 architectures), but even after that is resolved, it seems we still are unable to pull debug info out of the pcm file. I've filed pr37893 to track that, and I am disabling gmodules tests on linux until these issues are resolved. llvm-svn: 335235
Diffstat (limited to 'lldb/source/Plugins/ScriptInterpreter/Python/lldb-python.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud