Write adjusted range back to module

processor/minidump.cc

Index: processor/minidump.cc
diff --git a/processor/minidump.cc b/processor/minidump.cc
index 3e40f4fd1ad192399a820be958e03c633e3afcea..0ac2f9a919715af2942d9e2a1c3cf0d126b9bcb3 100644
--- a/processor/minidump.cc
+++ b/processor/minidump.cc
@@ -2327,6 +2327,13 @@ const MDImageDebugMisc* MinidumpModule::GetMiscRecord(uint32_t* size) {
   return reinterpret_cast<MDImageDebugMisc*>(&(*misc_record_)[0]);
 }
 
+void MinidumpModule::adjust_base_address_and_size(uint64_t base_address,
+                                                  uint64_t size) {
+  if (valid_) {
+    module_.base_of_image = base_address;
+    module_.size_of_image = size;
+  }
+}
 
 void MinidumpModule::Print() {
   if (!valid_) {
@@ -2635,6 +2642,7 @@ bool MinidumpModuleList::Read(uint32_t expected_size) {
                               HexString(module_size) << ", after adjusting";
               return false;
             }
+            module->adjust_base_address_and_size(base_address, module_size);

[Will Harris, 2016/05/02 22:25:43]

does this only apply to ashmem, or is this generic? if so can we remove the
kDevAshmem carve out entirely?

[michaelbai, 2016/05/02 22:33:13]

Yes, it only applies to ashmem.

[Will Harris, 2016/05/02 22:35:24]

Acknowledged.

           } else {
             BPLOG(ERROR) << "MinidumpModuleList could not store module " <<
                             module_index << "/" << module_count << ", " <<