{"id":466,"date":"2026-10-14T15:11:11","date_gmt":"2026-10-14T15:11:11","guid":{"rendered":"http:\/\/www.scmgalaxy.com\/tutorials\/2015\/12\/12\/20-pmap-commands-examples-in-linux-unix\/"},"modified":"2026-10-14T15:11:11","modified_gmt":"2026-10-14T15:11:11","slug":"20-pmap-commands-examples-in-linux-unix","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/20-pmap-commands-examples-in-linux-unix\/","title":{"rendered":"Linux pmap Command Guide: Inspect Process Memory Maps with Practical Examples"},"content":{"rendered":"\n

Originally published on 2015-12-12; fully revised and updated.<\/em><\/p>\n\n\n\n

The pmap<\/code> command reports the memory map of a running process. It is useful for Linux administrators, SREs, and developers who need more detail than ps<\/code> or top<\/code> provide. In this guide, you will learn when to use pmap<\/code>, how to use its most common options, and how to build a simple troubleshooting workflow for memory investigations.<\/p>\n\n\n\n

\"pmap<\/figure>\n\n\n\n

Why use pmap instead of only ps or top<\/h2>\n\n\n\n

Tools like ps<\/code> and top<\/code> are excellent for quick memory summaries, but they do not show the full mapping layout of a process. pmap<\/code> helps you inspect mapped regions and totals in one place, which is useful when diagnosing unexpected growth or understanding how memory is allocated.<\/p>\n\n\n\n

Tool or path<\/th>Best for<\/th>Strength<\/th>Limitation<\/th><\/tr><\/thead>
pmap<\/code><\/td>Per-process mapping inspection<\/td>Shows mappings and totals in readable output<\/td>Focused on one process at a time<\/td><\/tr>
ps<\/code><\/td>Quick process memory summary<\/td>Fast snapshot (RSS\/VSZ and more)<\/td>No detailed mapping breakdown<\/td><\/tr>
top<\/code>\/htop<\/code><\/td>Live monitoring<\/td>Continuous view of many processes<\/td>Not a deep memory map view<\/td><\/tr>
\/proc\/<pid>\/maps<\/code> and \/proc\/<pid>\/smaps<\/code><\/td>Low-level detail<\/td>Very detailed kernel-provided data<\/td>Manual parsing can be time-consuming<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Basic pmap syntax and quick start<\/h2>\n\n\n\n

The core syntax is simple: run pmap<\/code> with a process ID (PID).<\/p>\n\n\n

# Basic usage<\/span>\npmap 3724<\/span>\n\n# Find a PID first, then inspect it<\/span>\npgrep -n sshd\npmap $(pgrep -n sshd)<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>\n\n\n
For many builds of pmap<\/code>, the output includes a final total line. That line is commonly used as a quick memory checkpoint.<\/p>\n\n\n
pmap -x 3724 | tail -n 1<\/code><\/span><\/pre>\n\n\n
Common output modes and options<\/h2>\n\n\n\n
The original article highlighted the most frequently used options below.<\/p>\n\n\n\n
Option<\/th>What it does<\/th>Typical use<\/th><\/tr><\/thead>
pmap <pid><\/code><\/td>Shows default process mappings<\/td>Quick mapping overview<\/td><\/tr>
-x<\/code><\/td>Extended format with allocation details<\/td>Investigating RSS\/dirty-related detail per mapping<\/td><\/tr>
-d<\/code><\/td>Device format<\/td>Inspecting mapping\/device-oriented view<\/td><\/tr>
-q<\/code><\/td>Quiet mode (suppresses some header\/footer lines)<\/td>Scripting or compact output<\/td><\/tr>
-V<\/code><\/td>Shows program version<\/td>Checking behavior differences across environments<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n
pmap 3526\npmap -x 3526\npmap -d 3526\npmap -q 3526\npmap -V<\/code><\/span><\/pre>\n\n\n
Memory investigation workflow with pmap<\/h2>\n\n\n\n
When an application appears to consume too much memory, use a repeatable flow so you can compare snapshots and avoid guesswork.<\/p>\n\n\n\n
\nflowchart TD\n    A[Alert high memory] --> B[Find target PID]\n    B --> C[Check quick metrics with ps]\n    C --> D[Run pmap -x for detailed map]\n    D --> E{Need device view}\n    E -- yes --> F[Run pmap -d]\n    E -- no --> G[Review totals and large mappings]\n    F --> G\n    G --> H[Repeat checks over time]\n<\/pre>\n\n\n\n