Provided by: pcp_3.10.8build1_amd64 bug


       pmdbg - translate Performance Co-Pilot debug control flags


       pmdbg code ...
       pmdbg -l
       pmdbg -D name[,name ...]


       The  components  of  the  Performance  Co-Pilot (PCP) use a global vector of bit-fields to
       control diagnostic and debug output.

       pmdbg with a -l argument prints out the mnemonic and decimal values of all the  bit-fields
       in the debug control vector.

       pmdbg  with  a -D argument parses the list of names(s) using __pmParseDebug(3) and reports
       the corresponding decimal value.  This is most useful when debugging and  wanting  to  set
       the internal value of the control vector (pmDebug) via a debugger, e.g.  gdb(1).

       In the alternative usage, the code arguments are values for the debug vector, and the bit-
       fields that are enabled by each of these values is listed.

       Each code may be an integer, a hexadecimal value or a hexadecimal value prefixed by either
       ``0x'' or ``0X''.

       Most  applications  using  the  facilities of the PCP support a -DN command-line syntax to
       enable debug control.  pmdbg is designed to help choose an appropriate value for N.

       Alternatively the initial value of the debug control flags may be set to a value  N  using
       the  environment variable $PCP_DEBUG.  If both mechanisms are used the effect is additive,
       so the resultant flags are those set via $PCP_DEBUG combined with those  set  via  any  -D
       command line options.


       Environment variables with the prefix PCP_ are used to parameterize the file and directory
       names used by PCP.  On each installation, the file /etc/pcp.conf contains the local values
       for  these  variables.   The  $PCP_CONF  variable  may  be  used to specify an alternative
       configuration file, as described in pcp.conf(5).


       PCPIntro(1), pcp.conf(5) and pcp.env(5).