Adding PE TimeStamp to chrome trace to ease retrieving debug information

base/trace_event/process_memory_maps.cc

Index: base/trace_event/process_memory_maps.cc
diff --git a/base/trace_event/process_memory_maps.cc b/base/trace_event/process_memory_maps.cc
index a121239604074ebd2d4bfb4897f7b41fc46df03a..9f555d86acf48c00879e62f8d9240ad698dc405d 100644
--- a/base/trace_event/process_memory_maps.cc
+++ b/base/trace_event/process_memory_maps.cc
@@ -20,6 +20,7 @@ const uint32_t ProcessMemoryMaps::VMRegion::kProtectionFlagsMayshare = 128;
 ProcessMemoryMaps::VMRegion::VMRegion()
     : start_address(0),
       size_in_bytes(0),
+      timestamp(0),
       protection_flags(0),
       byte_stats_private_dirty_resident(0),
       byte_stats_private_clean_resident(0),
@@ -47,6 +48,8 @@ void ProcessMemoryMaps::AsValueInto(TracedValue* value) const {
 
     value->SetString("sa", StringPrintf(kHexFmt, region.start_address));
     value->SetString("sz", StringPrintf(kHexFmt, region.size_in_bytes));
+    if (region.timestamp)
+      value->SetString("ts", StringPrintf(kHexFmt, region.timestamp));
     value->SetInteger("pf", region.protection_flags);
     value->SetString("mf", region.mapped_file);