Don't muck with _LIBCPP_INLINE_VISIBILITY just to get predictable line table entries.
authorJim Ingham <jingham@apple.com>
Thu, 5 Jul 2018 23:11:27 +0000 (23:11 +0000)
committerJim Ingham <jingham@apple.com>
Thu, 5 Jul 2018 23:11:27 +0000 (23:11 +0000)
commit955535133976fb05add764479f192f1a4a9502af
tree158721b023bd027ff06be68b2c3d7cbc6e2fcafd
parentb2043ac72a1f1623fad47806f3e7881b7e70dcb4
Don't muck with _LIBCPP_INLINE_VISIBILITY just to get predictable line table entries.

This test was trying to stop at a variety of std::vector calls.  It looks like the test
was failing because various inlined std functions left no line table entries for the line that
invoked the inlined function.  The author worked around that by undefining _LIBCPP_INLINE_VISIBILITY.

That's an internal libcxx macro, we really shouldn't be playing around with it.  Better to just force
ourselves to stop where we want using some other non-inlineable statement.  printf seems a good candidate...

<rdar://problem/41867390>

llvm-svn: 336397
lldb/packages/Python/lldbsuite/test/functionalities/data-formatter/data-formatter-stl/libcxx/vector/main.cpp