Chromium Code Reviews| 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 31083a892773ad3fb268ecadfaa247c18b5fffaf..9fbee95c9029642be6f347b6d24afecbdd8ed983 100644 |
| --- a/base/trace_event/process_memory_maps.cc |
| +++ b/base/trace_event/process_memory_maps.cc |
| @@ -15,6 +15,7 @@ namespace trace_event { |
| const uint32_t ProcessMemoryMaps::VMRegion::kProtectionFlagsRead = 4; |
| const uint32_t ProcessMemoryMaps::VMRegion::kProtectionFlagsWrite = 2; |
| const uint32_t ProcessMemoryMaps::VMRegion::kProtectionFlagsExec = 1; |
| +const uint32_t ProcessMemoryMaps::VMRegion::kProtectionFlagsMayShare = 80; |
|
Primiano Tucci (use gerrit)
2016/02/05 09:32:39
80 ??
I guess you meant 8
petrcermak
2016/02/05 11:18:56
nit: Is there a reason why these are not sorted in
petrcermak
2016/02/05 11:21:34
Also, could you please provide a link to some docu
Primiano Tucci (use gerrit)
2016/02/11 13:51:48
yeah, this is either 0x80 or 128 but definitely no
|
| ProcessMemoryMaps::VMRegion::VMRegion() |
| : start_address(0), |