CALLGRIND CONTROL(1)           Release 3.15.0           CALLGRIND CONTROL(1)

NAME         top

       callgrind_control - observe and control programs being run by

SYNOPSIS         top

       callgrind_control [options] [pid|program-name...]

DESCRIPTION         top

       callgrind_control controls programs being run by the Valgrind tool
       Callgrind. When a pid/program name argument is not specified, all
       applications currently being run by Callgrind on this system will be
       used for actions given by the specified option(s). The default action
       is to give some brief information about the applications being run by

OPTIONS         top

       -h --help
           Show a short description, usage, and summary of options.

           Show version of callgrind_control.

       -l --long
           Show also the working directory, in addition to the brief
           information given by default.

       -s --stat
           Show statistics information about active Callgrind runs.

       -b --back
           Show stack/back traces of each thread in active Callgrind runs.
           For each active function in the stack trace, also the number of
           invocations since program start (or last dump) is shown. This
           option can be combined with -e to show inclusive cost of active

       -e [A,B,...]  (default: all)
           Show the current per-thread, exclusive cost values of event
           counters. If no explicit event names are given, figures for all
           event types which are collected in the given Callgrind run are
           shown. Otherwise, only figures for event types A, B, ... are
           shown. If this option is combined with -b, inclusive cost for the
           functions of each active stack frame is provided, too.

       --dump[=<desc>]  (default: no description)
           Request the dumping of profile information. Optionally, a
           description can be specified which is written into the dump as
           part of the information giving the reason which triggered the
           dump action. This can be used to distinguish multiple dumps.

       -z --zero
           Zero all event counters.

       -k --kill
           Force a Callgrind run to be terminated.

           Switch instrumentation mode on or off. If a Callgrind run has
           instrumentation disabled, no simulation is done and no events are
           counted. This is useful to skip uninteresting program parts, as
           there is much less slowdown (same as with the Valgrind tool
           "none"). See also the Callgrind option --instr-atstart.

           Specify the vgdb prefix to use by callgrind_control.
           callgrind_control internally uses vgdb to find and control the
           active Callgrind runs. If the --vgdb-prefix option was used for
           launching valgrind, then the same option must be given to

SEE ALSO         top

       valgrind(1), $INSTALL/share/doc/valgrind/html/index.html or

AUTHOR         top

       Josef Weidendorfer <>.

COLOPHON         top

       This page is part of the valgrind (a system for debugging and
       profiling Linux programs) project.  Information about the project can
       be found at ⟨⟩.  If you have a bug report for
       this manual page, see
       ⟨⟩.  This page was
       obtained from the project's upstream Git repository
       ⟨⟩ on 2019-05-09.  (At that
       time, the date of the most recent commit that was found in the repos‐
       itory was 2019-05-08.)  If you discover any rendering problems in
       this HTML version of the page, or you believe there is a better or
       more up-to-date source for the page, or you have corrections or
       improvements to the information in this COLOPHON (which is not part
       of the original manual page), send a mail to

Release 3.15.0                   05/09/2019             CALLGRIND CONTROL(1)

Pages that refer to this page: valgrind(1)