diff options
| author | Pavel Labath <pavel@labath.sk> | 2018-08-31 18:25:01 +0000 |
|---|---|---|
| committer | Pavel Labath <pavel@labath.sk> | 2018-08-31 18:25:01 +0000 |
| commit | 332447f4b45f48d1ce5c4ecc25504cdfadfd2ce2 (patch) | |
| tree | 616f0bd18ae4d0756551f7a03c93ac647150e0b7 /lldb/packages/Python/lldbsuite/test/functionalities/data-formatter | |
| parent | 2aa8efc820664769948f76599fa416722de22e06 (diff) | |
| download | bcm5719-llvm-332447f4b45f48d1ce5c4ecc25504cdfadfd2ce2.tar.gz bcm5719-llvm-332447f4b45f48d1ce5c4ecc25504cdfadfd2ce2.zip | |
Avoid using short identifiers in some tests
This applies the same workaround as r321271 to other tests. The root
problem is that lldb finds an internal symbol with the same name in the
debug info of system libraries, and then fails to disambiguate between
the two.
llvm-svn: 341235
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/data-formatter')
| -rw-r--r-- | lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-synthval/TestDataFormatterSynthVal.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-synthval/TestDataFormatterSynthVal.py b/lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-synthval/TestDataFormatterSynthVal.py index 08768a61bd9..23b0dfb8f8a 100644 --- a/lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-synthval/TestDataFormatterSynthVal.py +++ b/lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-synthval/TestDataFormatterSynthVal.py @@ -107,7 +107,7 @@ class DataFormatterSynthValueTestCase(TestBase): # check that an aptly defined synthetic provider does not affect # one-lining self.expect( - "expression struct S { myInt theInt{12}; }; S()", + "expression struct Struct { myInt theInt{12}; }; Struct()", substrs=['(theInt = 12)']) # check that we can use a synthetic value in a summary |
