summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct/main.cpp
diff options
context:
space:
mode:
authorAdrian McCarthy <amccarth@google.com>2018-02-26 21:22:39 +0000
committerAdrian McCarthy <amccarth@google.com>2018-02-26 21:22:39 +0000
commit00cc735a6f443cec8d9fcd3d64ae8d10a7caaae0 (patch)
tree02f867be7202bbde9d96f0769cf33d1d99a89369 /lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct/main.cpp
parenta04793eb933bbcab515862dc9c4da699e1ec7f24 (diff)
downloadbcm5719-llvm-00cc735a6f443cec8d9fcd3d64ae8d10a7caaae0.tar.gz
bcm5719-llvm-00cc735a6f443cec8d9fcd3d64ae8d10a7caaae0.zip
Partial fix for TestConflictingSymbol.py on Windows
Without this fix, the test ERRORs because the link of the inferior fails. This patch adds the LLDB_TEST_API macro where needed and uses the new -2 magic value for num_expected_locations to account for lazy-loading of module symbols on Windows. With this fix, the test itself still fails: conflicting_symbol isn't in the debug info nor the export table, and Windows binaries don't have an equivalent of the ELF .symtab. We need to understand why the test works to keep the symbol out of the debug info. In the mean time, having the test fail at this point is a better indication of the remaining problem than a build error. Differential Revision: https://reviews.llvm.org/D43688 llvm-svn: 326130
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/expression_command/anonymous-struct/main.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud