Link to native_heapdump_viewer.py.
Bug: N/A
Test: N/A
Change-Id: I1e448f30922d948513ebb65abc25c474ffbd5a24
diff --git a/libc/malloc_debug/README.md b/libc/malloc_debug/README.md
index b50de40..18d22a4 100644
--- a/libc/malloc_debug/README.md
+++ b/libc/malloc_debug/README.md
@@ -534,7 +534,8 @@
/system/libutils.so which starts at 0xb000. The relative pc is 0x510 and
it is in an unknown function.
-There is a tool to visualize this data, development/scripts/native\_heapdump\_viewer.py.
+There is a tool to visualize this data,
+[native\_heapdump\_viewer.py](https://android.googlesource.com/platform/development/+/master/scripts/native_heapdump_viewer.py).
Examples
========
@@ -637,9 +638,8 @@
### Analyzing heap dumps
-To analyze the data produced by the dumpheap command, run this script:
-
- development/scripts/native_heapdump_viewer.py
+To analyze the data produced by the dumpheap command, run
+[development/scripts/native\_heapdump\_viewer.py](https://android.googlesource.com/platform/development/+/master/scripts/native_heapdump_viewer.py)
In order for the script to properly symbolize the stacks in the file,
make sure the script is executed from the tree that built the image.