[tracing] Introduce MemoryDumpArgs to enable light and heavy dumps

base/trace_event/process_memory_maps_dump_provider.cc

Index: base/trace_event/process_memory_maps_dump_provider.cc
diff --git a/base/trace_event/process_memory_maps_dump_provider.cc b/base/trace_event/process_memory_maps_dump_provider.cc
index e0ae20d2a5b02fdab8c750c3c1ce9723fe584ffd..f332024a82e7e865e070a09063be3ec02a9b1a2e 100644
--- a/base/trace_event/process_memory_maps_dump_provider.cc
+++ b/base/trace_event/process_memory_maps_dump_provider.cc
@@ -165,7 +165,11 @@ ProcessMemoryMapsDumpProvider::~ProcessMemoryMapsDumpProvider() {
 
 // Called at trace dump point time. Creates a snapshot the memory maps for the

[petrcermak, 2015/08/03 10:12:35]

When you're already touching this file, could you please make the following
change in this comment:

s/snapshot the memory maps/snapshot of the memory maps/

[ssid, 2015/08/03 10:34:02]

Done.

 // current process.
-bool ProcessMemoryMapsDumpProvider::OnMemoryDump(ProcessMemoryDump* pmd) {
+bool ProcessMemoryMapsDumpProvider::OnMemoryDump(const MemoryDumpArgs& args,
+                                                 ProcessMemoryDump* pmd) {
+  // TODO(ssid): Use MemoryDumpArgs to create light dumps when requested
+  // (crbug.com/499731).
+
   uint32 res = 0;
 
 #if defined(OS_LINUX) || defined(OS_ANDROID)