Added scripts to analyze sanitizer poisoning
Scripts are meant to be used in conjunction with DexFileTrackingRegistrar.
After poisoning certain sections of a dex file, the logcat will contain
traces in addition to information of dex files. This is used in order to
condense the large amount of information that is dumped into the logcat.
Bug: 37754950
Test: art/tools/runtime_memusage/sanitizer_logcat_analysis.sh
[LOGCAT_FILE]
Change-Id: Ied28e09899ec097f09332784bf80481f9c7dcb3f
diff --git a/runtime/dex_file_tracking_registrar.cc b/runtime/dex_file_tracking_registrar.cc
index f41a50b..848e2f3 100644
--- a/runtime/dex_file_tracking_registrar.cc
+++ b/runtime/dex_file_tracking_registrar.cc
@@ -69,7 +69,10 @@
// Intended for local changes only.
void DexFileTrackingRegistrar::SetDexSections() {
- if (kDexFileAccessTracking || dex_file_ != nullptr) {
+ if (kDexFileAccessTracking && dex_file_ != nullptr) {
+ // Logs the Dex File's location and starting address if tracking is enabled
+ LOG(ERROR) << "RegisterDexFile: " << dex_file_->GetLocation() + " @ " << std::hex
+ << reinterpret_cast<uintptr_t>(dex_file_->Begin());
switch (kCurrentTrackingSystem) {
case kWholeDexTracking:
SetDexFileRegistration(true);