================ @@ -0,0 +1,45 @@ +""" +Standalone reproducer for the lookup failure originally seen in +TestAbiTagLookup.py on Apple platforms, where the dyld shared cache +happens to expose two internal data symbols literally named `v1`. + +This test plants two unrelated internal data symbols named +`colliding_ns` in non-debug-info objects, then evaluates a qualified-id +expression that uses `colliding_ns` as a (real) namespace prefix. + +Expected eventual behavior: the namespace resolution succeeds and the +function call returns 6. + +Current behavior (XFAIL): ClangExpressionDeclMap falls through to +SymbolContext::FindBestGlobalDataSymbol which sees two internal +`colliding_ns` data symbols and raises + "error: Multiple internal symbols found for 'colliding_ns'" +even though the name has already been resolved to a NamespaceDecl +earlier in the same lookup. +""" + +import lldb +from lldbsuite.test.decorators import * +from lldbsuite.test.lldbtest import * +from lldbsuite.test import lldbutil + + +class NamespaceDataSymbolCollisionTestCase(TestBase): ---------------- Teemperor wrote:
You can just name this `class TestCase(TestBase):`. There is little benefit for duplicating the file name in the class and we stopped doing that in newer tests. Also, the test case name gets prepended to the build directory, and long test names unfortunately tend to break on Windows with its short character limit. https://github.com/llvm/llvm-project/pull/203984 _______________________________________________ lldb-commits mailing list [email protected] https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
