libbinder_ndk: dump class ptrs in assoc. failure
We know nothing about them if they mismatch now. This could help us
figure out certain kind of memory corruption issues or, if we dump
process memory and have access to mapping information, determine where
the globals that refer to these different classes come from
(AIBinder_Class ptrs are usually stored in globals).
Bug: 195473723
Test: see log in logcat
Change-Id: I3010b62d70a63114fa4610d25860d3602740e185
diff --git a/libs/binder/ndk/ibinder.cpp b/libs/binder/ndk/ibinder.cpp
index 2abb6f7..11e9fc5 100644
--- a/libs/binder/ndk/ibinder.cpp
+++ b/libs/binder/ndk/ibinder.cpp
@@ -82,8 +82,8 @@
const String16& currentDescriptor = mClazz->getInterfaceDescriptor();
if (newDescriptor == currentDescriptor) {
LOG(ERROR) << __func__ << ": Class descriptors '" << currentDescriptor
- << "' match during associateClass, but they are different class objects. "
- "Class descriptor collision?";
+ << "' match during associateClass, but they are different class objects ("
+ << clazz << " vs " << mClazz << "). Class descriptor collision?";
} else {
LOG(ERROR) << __func__
<< ": Class cannot be associated on object which already has a class. "