Proc Maps
Inspect Linux memory mappings with exact address ranges, virtual-memory totals and line errors.
About this tool
Paste Linux /proc/<pid>/maps text and parse it. The example is editable. Summaries show classes and virtual mapped sizes; switch to By file or Mappings for paths, addresses, permissions, file offset, device and inode. Exact bytes are available on size values.
Addresses and totals use BigInt. Sizes and percentages are truncated to two and one decimal places respectively; these are virtual mappings, not resident memory. Class names are heuristics, not an ELF analysis. Executable anonymous memory takes precedence over writable memory. Deleted-file suffixes and path spaces remain intact.
Malformed fields, reversed/empty ranges and overlapping ranges are excluded with line numbers. Entries are sorted by address; the first accepted interval in that order wins. Editing clears old results.
Draft text and search settings are saved locally when they fit the shared browser-storage limit (100,000 serialized characters). Larger dumps keep the previous saved copy and show a warning: download the full text before reload or navigation. Analysis supports 20,000 physical lines, including a final newline, and 2,000,000 characters. Detail tables are built on demand and split into pages of 200 rows. Find mapping matches paths, permissions, devices and inodes without case sensitivity; enter a hexadecimal 0x address to find the region containing it (start included, end excluded). Searching only filters the mapping table; whole-dump totals and summaries stay unchanged.
Only source text and the search query are saved, never computed summaries or result pages. Reopening requires Analyze; Example displays its small analysis immediately. Pathnames keep literal spaces and the kernel’s \012 spelling; this notation and the (deleted) suffix can be ambiguous and are not decoded.
When a saved search is present, analysis opens Mappings directly. The page controls are above the table.
An address match shows the hexadecimal distance from the mapping start and, for a mapping with an inode, the calculated file offset.