> Analysts and supporters often use /proc/xx/maps to make sense of the memory > footprint of a process. > > Interpreting the memory map correctly can help when used as a complement to > other tools (e.g. NMT). There even exist tools out there that attempt to > annotate the process memory map with JVM information. > > That, however, can be more accurately done from within the JVM, at least for > mappings originating from hotspot. After all, we can correlate the mapping > information in NMT with the VMA map. > > Example output (from a spring petstore run): > > [example_system_map.txt](https://github.com/openjdk/jdk/files/13179054/example_system_map.txt) > > This patch adds the VM annotations for VMAs that are *mmaped*. I also have an > experimental patch that works with malloc'ed memory, but it is not ready yet > for consumption and I leave that part of for now.
Thomas Stuefe has updated the pull request incrementally with one additional commit since the last revision: remove remnants of os::realpath ------------- Changes: - all: https://git.openjdk.org/jdk/pull/16301/files - new: https://git.openjdk.org/jdk/pull/16301/files/050656a0..e181298b Webrevs: - full: https://webrevs.openjdk.org/?repo=jdk&pr=16301&range=10 - incr: https://webrevs.openjdk.org/?repo=jdk&pr=16301&range=09-10 Stats: 10 lines in 2 files changed: 0 ins; 10 del; 0 mod Patch: https://git.openjdk.org/jdk/pull/16301.diff Fetch: git fetch https://git.openjdk.org/jdk.git pull/16301/head:pull/16301 PR: https://git.openjdk.org/jdk/pull/16301
