Lines Matching full:program
18 functions in a program's run as a call-graph.
27 <para>The profile data is written out to a file at program
49 the status of a program currently running under Callgrind's control,
50 without stopping the program. You can get statistics information as
69 <function>foo</function>'s costs. When applied to the program as a whole,
76 of the total program cost. Because of costs arising before
80 is not exactly 100 percent of the total program cost.</para>
85 program's costs occur. Caller/callee cost attribution is also useful
110 <para>To start a profile run for a program, execute:
111 <screen>valgrind --tool=callgrind [callgrind options] your-program [program options]</screen>
121 <para>After program termination, a profile data file named
124 of the program being profiled.
126 program among the functions executed, together with
178 cache behavior of your program, use Callgrind with the option
183 <para>If the program section you want to profile is somewhere in the
212 xreflabel="Multiple dumps from one program run">
213 <title>Multiple profiling dumps from one program run</title>
216 program run, but only of a small part of it, for example execution of one
219 profile information for different parts of a single program run.</para>
227 program, <emphasis>part</emphasis> is a number incremented on each
228 dump (".part" is skipped for the dump at program termination), and
234 while a program is running under Callgrind's supervision. Nevertheless,
236 information since the last dump or program start, and zero cost
243 <para><command>Dump on program termination.</command>
254 distinguish profile dumps. The control program will not terminate
287 <para><command>Program controlled dumping.</command>
319 for program code is enabled. This is the default, but for faster
321 it can be disabled until the program reaches a state in which
334 event collection for the parts of your program you are interested in.
342 at program start is "off". Only events happening while running
396 cycles be avoided without changing program code?</para>
409 <para>Now, when a program exposes really big cycles (as is
429 does not do any cycle detection at all. For program executions with function
435 program. Instead, the symbol name could encode additional information
466 in your program, you usually get a "false" cycle "B <> C". Use
482 <para>If your program forks, the child will inherit all the profiling
687 profiling from the beginning of the program.
702 instrumentation later in the program run, as the simulator starts
715 <para>To only look at parts of your program, you have two
719 <para>Zero event counters before entering the program part you
721 leaving that program part.</para>
725 event counters happening while inside of the program part you
729 <para>The second option can be used if the program part you want to
1307 specified Callgrind runs by providing a list of pids or program names as
1349 since program start (or last dump) is shown. This option can be
1396 counted. This is useful to skip uninteresting program parts, as there
