Lines Matching full:dump
196 <option><xref linkend="opt.dump-instr"/>=yes</option>. This will produce
228 dump (".part" is skipped for the dump at program termination), and
235 all methods trigger the same action, which is "dump all profile
236 information since the last dump or program start, and zero cost
243 <para><command>Dump on program termination.</command>
255 before the dump is completely written. Note that the application
256 must be actively running for detection of the dump command. So,
261 button <command>Force dump</command>. This will request a dump
262 and trigger a reload after the dump is written.</para>
268 option <option><xref linkend="opt.dump-every-bb"/>=count</option>.
275 option <option><xref linkend="opt.dump-before"/>=function</option>
276 and <option><xref linkend="opt.dump-after"/>=function</option>.
281 <option><xref linkend="opt.dump-before"/>='foo*'</option> to
289 <computeroutput><xref linkend="cr.dump-stats"/>;</computeroutput>
290 at the position in your code where you want a profile dump to happen. Use
301 profile dump. Thus, the last two methods will only generate one dump
303 multiple dumps (one for each thread) on a dump request.</para>
511 <option><xref linkend="opt.dump-before"/>=function</option>, or
522 xreflabel="Dump creation options">
523 <title>Dump creation options</title>
550 <varlistentry id="opt.dump-line" xreflabel="--dump-line">
552 <option><![CDATA[--dump-line=<no|yes> [default: yes] ]]></option>
562 <varlistentry id="opt.dump-instr" xreflabel="--dump-instr">
564 <option><![CDATA[--dump-instr=<no|yes> [default: no] ]]></option>
626 <varlistentry id="opt.dump-every-bb" xreflabel="--dump-every-bb">
628 <option><![CDATA[--dump-every-bb=<count> [default: 0, never] ]]></option>
631 <para>Dump profile data every <option>count</option> basic blocks.
632 Whether a dump is needed is only checked when Valgrind's internal
634 The count is a 64-bit value to make long dump periods possible.
639 <varlistentry id="opt.dump-before" xreflabel="--dump-before">
641 <option><![CDATA[--dump-before=<function> ]]></option>
644 <para>Dump when entering <option>function</option>.</para>
657 <varlistentry id="opt.dump-after" xreflabel="--dump-after">
659 <option><![CDATA[--dump-after=<function> ]]></option>
662 <para>Dump when leaving <option>function</option>.</para>
720 want to profile, and dump the event counters to a file after
1086 <para><varname>dump [<dump_hint>]</varname> requests to dump the
1118 <varlistentry id="cr.dump-stats" xreflabel="CALLGRIND_DUMP_STATS">
1123 <para>Force generation of a profile dump at specified position
1129 <varlistentry id="cr.dump-stats-at" xreflabel="CALLGRIND_DUMP_STATS_AT">
1349 since program start (or last dump) is shown. This option can be
1368 <term><option><![CDATA[--dump[=<desc>] ]]></option> (default: no description)</term>
1371 description can be specified which is written into the dump as part of
1372 the information giving the reason which triggered the dump action. This
