jingham added a comment. Yes, that usage is exactly the sort of use I was talking about. When we get an ObjC object and want to find its dynamic type, we read the type name by following the object's ISA pointer to the Class object. Then we go to look up the type from that name. We know we want an exact match to the name we found, but there's nothing that says the same module can't have an C++ class with the same name as an ObjC class. So that code needs to get all the types found, and sort through them for the one that is an ObjC interface type, and discard all the others. You will need to support that behavior somehow.
https://reviews.llvm.org/D53662 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
