summaryrefslogtreecommitdiffstats
path: root/third_party/libxslt
diff options
context:
space:
mode:
authorpliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-06-05 14:07:33 +0000
committerpliard@chromium.org <pliard@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-06-05 14:07:33 +0000
commit21c9f94feb395b8755277fdff553122ffc04beea (patch)
tree3910aa814e2e79b1071ca9ed3930aa91d3e2993a /third_party/libxslt
parentb090de9f1bef13cad16fbec4a50909993f51aa78 (diff)
downloadchromium_src-21c9f94feb395b8755277fdff553122ffc04beea.zip
chromium_src-21c9f94feb395b8755277fdff553122ffc04beea.tar.gz
chromium_src-21c9f94feb395b8755277fdff553122ffc04beea.tar.bz2
Add tools/android/memdump/.
This adds the 'memdump' binary that dumps device memory information for a list of processes and 'memreport.py' (executed on the host) used to process this information. Memdump is similar to /proc/<PID>/smaps except that it is multi-process aware. For a list of processes (e.g. browser + renderer processes), it is able to dinstinguish the memory pages that are mapped only in these processes from the ones that are private or also mapped in external processes. This is useful to gather high level memory usage information (e.g. heap size vs code size) for any (non-instrumented) process. R=bulach@chromium.org, digit@chromium.org, qsr@chromium.org Review URL: https://codereview.chromium.org/15861023 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@204254 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'third_party/libxslt')
0 files changed, 0 insertions, 0 deletions