• Home
Name Date Size #Lines LOC

..--

scripts/03-May-2024-476306

DEPSD03-May-202433 43

READMED03-May-2024721 1812

call_stack.ccD03-May-202413.4 KiB400307

call_stack.hD03-May-20245.3 KiB16978

dllmain.ccD03-May-20244.5 KiB156101

hotkey.hD03-May-20241.2 KiB4932

ia32_modrm_map.ccD03-May-20243.6 KiB9572

ia32_opcode_map.ccD03-May-2024106.5 KiB1,1621,100

memory_hook.ccD03-May-202419.3 KiB563388

memory_hook.hD03-May-20244.4 KiB15477

memory_watcher.ccD03-May-20247.5 KiB256181

memory_watcher.gypD03-May-20241.3 KiB4947

memory_watcher.hD03-May-20242.7 KiB9642

mini_disassembler.ccD03-May-202413.8 KiB393261

mini_disassembler.hD03-May-20246.2 KiB16438

mini_disassembler_types.hD03-May-20246.5 KiB200108

preamble_patcher.ccD03-May-20249.6 KiB229142

preamble_patcher.hD03-May-202412.3 KiB29476

preamble_patcher_with_stub.ccD03-May-20247.4 KiB17586

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