Wow, thanks WenSheng for summarizing it! I was just thinking about documenting dmprof-internals.
Some points:
1) I didn't give a specific name to the in-Chromium dumper. If you want to call it, using the filename (deep_heap_profile.cc) may be better to avoid misunderstanding.
2) Similarly, calling third_party/tcmalloc/chromium/src/heap-profiler.cc as "gperftools' heap profiler" can avoid misunderstanding. (There are other "Heap Profilers".)
3) Finally about naming, "dmprof" sometimes means all the workflow from the dumper to the analyzer script. Calling it "the dmprof post-mortem analyzer" can avoid misunderstanding.
4) RTTI is not necessary if we don't use the type profiler. RTTI is used only by the type profiler. The dmprof script converts a virtual address to a function name only from a symbol table. Note that RTTI and a symbol table are different things. (src/tools/find_runtime_symbols/*.py really does it.)