1PMDBG(1) General Commands Manual PMDBG(1)
2
3
4
6 pmdbg - translate Performance Co-Pilot debug control flags
7
9 pmdbg code ...
10 pmdbg -l
11 pmdbg -D name[,name ...]
12
14 The components of the Performance Co-Pilot (PCP) use a global vector of
15 bit-fields to control diagnostic and debug output.
16
17 pmdbg with a -l argument prints out the mnemonic and decimal values of
18 all the bit-fields in the debug control vector.
19
20 pmdbg with a -D argument parses the list of names(s) using __pmParseDe‐
21 bug(3) and reports the corresponding decimal value. This is most use‐
22 ful when debugging and wanting to set the internal value of the control
23 vector (pmDebug) via a debugger, e.g. gdb(1).
24
25 In the alternative usage, the code arguments are values for the debug
26 vector, and the bit-fields that are enabled by each of these values is
27 listed.
28
29 Each code may be an integer, a hexadecimal value or a hexadecimal value
30 prefixed by either ``0x'' or ``0X''.
31
32 Most applications using the facilities of the PCP support a -DN com‐
33 mand-line syntax to enable debug control. pmdbg is designed to help
34 choose an appropriate value for N.
35
36 Alternatively the initial value of the debug control flags may be set
37 to a value N using the environment variable $PCP_DEBUG. If both mecha‐
38 nisms are used the effect is additive, so the resultant flags are those
39 set via $PCP_DEBUG combined with those set via any -D command line
40 options.
41
43 Environment variables with the prefix PCP_ are used to parameterize the
44 file and directory names used by PCP. On each installation, the file
45 /etc/pcp.conf contains the local values for these variables. The
46 $PCP_CONF variable may be used to specify an alternative configuration
47 file, as described in pcp.conf(5).
48
50 PCPIntro(1), pcp.conf(5) and pcp.env(5).
51
52
53
54Performance Co-Pilot PCP PMDBG(1)