• Home
  • History
  • Annotate
  • only in /external/chromium_org/tools/memory_watcher/
NameDateSize

..03-Jan-20144 KiB

call_stack.cc03-Jan-201413.4 KiB

call_stack.h03-Jan-20145.3 KiB

DEPS03-Jan-201447

dllmain.cc03-Jan-20144.5 KiB

hotkey.h03-Jan-20141.2 KiB

ia32_modrm_map.cc03-Jan-20143.6 KiB

ia32_opcode_map.cc03-Jan-2014106.5 KiB

memory_hook.cc03-Jan-201419.2 KiB

memory_hook.h03-Jan-20144.4 KiB

memory_watcher.cc03-Jan-20147.5 KiB

memory_watcher.gyp03-Jan-20141.2 KiB

memory_watcher.h03-Jan-20142.7 KiB

mini_disassembler.cc03-Jan-201413.8 KiB

mini_disassembler.h03-Jan-20146.2 KiB

mini_disassembler_types.h03-Jan-20146.5 KiB

preamble_patcher.cc03-Jan-20149.6 KiB

preamble_patcher.h03-Jan-201412.3 KiB

preamble_patcher_with_stub.cc03-Jan-20147.4 KiB

README03-Jan-2014721

scripts/03-Jan-20144 KiB

README

1memory_watcher is a library that can be linked into chromium to trace the
2memory allocations. It works by hooking the system allocation/deallocation
3functions, and recording the actions.
4
5To use memory_watcher in chromium:
6
7(1) Compile the memory_watcher library (it is part of the solution by default)
8
9(2) Run chromium with these flags "--memory-profile -no-sandbox"
10(The instrumentation doesn't work with the sandbox)
11
12(3) Hit ctrl-alt-D  to generate a dump of the memory allocations.
13This will create a log file called memorywatcher.logXXXX for every
14chromium process (where XXXX is the pid).
15
16The log file is a human readable text format, which can be further analyzed
17using the helpers in the "scripts/" directory.
18