Home
last modified time | relevance | path

Searched refs:mmaps (Results 1 – 8 of 8) sorted by relevance

/external/chromium-trace/catapult/telemetry/telemetry/timeline/
Dmemory_dump_event_unittest.py12 mmaps=None, allocators=None): argument
29 if mmaps:
32 for mapped_file, byte_stats in mmaps.iteritems()]}
37 def TestProcessDumpEvent(dump_id='123456ABCDEF', pid=1234, start=0, mmaps=None, argument
39 event = MakeRawMemoryDumpEvent(dump_id, pid, start, mmaps=mmaps,
94 memory_dump = TestProcessDumpEvent(mmaps={
126 mmaps = {'/dev/ashmem/dalvik-space-foo': {'pss': java_spaces}}
129 MakeRawMemoryDumpEvent(pid=process.pid, mmaps=mmaps)]
149 mmaps={'/dev/ashmem/other-ashmem': {'pss': 5}},
152 mmaps={'/dev/ashmem/libc malloc': {'pss': 42, 'pd': 27}},
[all …]
/external/compiler-rt/lib/asan/
Dasan_stats.h37 uptr mmaps; member
Dasan_stats.cc52 mmaps, munmaps); in Print()
Dasan_allocator.cc180 thread_stats.mmaps++; in OnMap()
/external/valgrind/docs/internals/
Dsegments-seginfos.txt25 range which is not yet mmaped. For example, if the process mmaps the
40 which just mmaps ELF files but just uses it as raw data (copy, for
43 Valgrind doesn't control the mmaps. It just observes the mmaps
D3_2_BUGSTATUS.txt404 r6495 r6497 32 n-i-bz More robust handling of hinted client mmaps
/external/valgrind/
DNEWS.old376 n-i-bz More robust handling of hinted client mmaps
DNEWS973 - Valgrind no longer temporarily mmaps the entire object to read