Adding PE TimeStamp to chrome trace to ease retrieving debug information

base/trace_event/process_memory_maps.h

Index: base/trace_event/process_memory_maps.h
diff --git a/base/trace_event/process_memory_maps.h b/base/trace_event/process_memory_maps.h
index 6a7367437e55d0208ade37130b1ea08fcbf009d2..35bb6e53ef5ce71f67401c6b2dd6eba5af8ff5cb 100644
--- a/base/trace_event/process_memory_maps.h
+++ b/base/trace_event/process_memory_maps.h
@@ -32,6 +32,7 @@ class BASE_EXPORT ProcessMemoryMaps {
 
     uint64_t start_address;
     uint64_t size_in_bytes;
+    uint64_t timestamp;

[Primiano Tucci (use gerrit), 2017/05/09 16:34:01]

since this is windows only can we call it win_module_timestamp or something like
that?
Otherwise this sounds like a "timestamp of the mmap" that "ourselves from the
future" will find quite hard to understand.

[etienneb, 2017/05/09 17:39:31]

Agree that adding module_ will help understanding that it's not the timestamp of
the mmap.

I'm not a fan of win_ prefix.

     uint32_t protection_flags;
     std::string mapped_file;