Add an expectedFailure test for type finding.
authorJim Ingham <jingham@apple.com>
Thu, 18 Jul 2019 22:21:16 +0000 (22:21 +0000)
committerJim Ingham <jingham@apple.com>
Thu, 18 Jul 2019 22:21:16 +0000 (22:21 +0000)
commitfa6199bc5d374d8d0aa81570b30fdb6454e43eb0
treed05b3bd25ecf8a84b711850f5bf4f3f4b2e9c0fd
parentee515d3d03e998e91917881e6401801fa5340b71
Add an expectedFailure test for type finding.

When two .c files define a type of the same name, lldb
just picks one and uses it regardless of context.  That is
not correct.  When stopped in a frame in one of the .c files
that define this type, it should use that local definition.

This commit just adds a test that checks for the correct
behavior.  It is currently xfailed.

llvm-svn: 366507
lldb/packages/Python/lldbsuite/test/lang/c/local_types/TestUseClosestType.py [new file with mode: 0644]
lldb/packages/Python/lldbsuite/test/lang/c/local_types/main.c [new file with mode: 0644]
lldb/packages/Python/lldbsuite/test/lang/c/local_types/other.c [new file with mode: 0644]