summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp/extern_c
diff options
context:
space:
mode:
authorPavel Labath <labath@google.com>2017-12-21 14:40:03 +0000
committerPavel Labath <labath@google.com>2017-12-21 14:40:03 +0000
commit3db29a1b3ea5b896dd4e90cd2d739e5f687ebc7a (patch)
tree20bd85513e5ebb9b87066f75ab26670952ed8ca0 /lldb/packages/Python/lldbsuite/test/lang/cpp/extern_c
parente8d84a67c2c5fb0219251c5f4112a77a7260f554 (diff)
downloadbcm5719-llvm-3db29a1b3ea5b896dd4e90cd2d739e5f687ebc7a.tar.gz
bcm5719-llvm-3db29a1b3ea5b896dd4e90cd2d739e5f687ebc7a.zip
Work around test failures on red-hat linux
Two tests were failing because the debugger was picking up multiply defined internal symbols from the system libraries. This is a bug, as there should be no ambiguity because the tests are defining variables with should shadow these symbols, but lldb is not smart enough to figure that out. I work around the issue by renaming the variables in these tests, and in exchange I create a self-contained test which reproduces the issue without depending on the system libraries. This increases the predictability of our test suite. llvm-svn: 321271
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp/extern_c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud