Hide Forgot
Description of problem: Please add a short description of the columns shown in the 'pmap -x' output. Some columns are self-explanatory like Address and KBytes, but RSS and Dirty may not be quite as obvious if you're not familiar with Linux virtual memory terminology. Columns include Address, Kbytes, RSS, Dirty, Mode, and Mapping Version-Release number of selected component (if applicable): procps-3.2.7-16.el5
Possible definitions for pmap(1) man page: Address: start address of map Kbytes: size of map in kilobytes RSS: resident set size in kilobytes Dirty: dirty pages (both shared and private) in kilobytes Mode: permissions on map: read, write, execute, shared, private (copy on write) Mapping: file backing the map, or '[ anon ]' for allocated memory, or '[ stack ]' for the program stack See proc(5) man page for more details.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Fixed in procps-3.2.7-17.el5.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause pmap manual page doesn't describe displayed columns Consequence user doesn't know what each column means Fix manual page update Result columns are described in manual page
Fix was tested on package procps-3.2.7-17.el5. Manual page now contains description of column names.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-0459.html