request. Update/clarify documentation.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5806
CLG_(clo).dump_bb = False;
else if (0 == VG_(strncmp)(arg, "--dump-every-bb=", 16))
- CLG_(clo).dump_every_bb = (Int)VG_(atoll)(&arg[16]);
+ CLG_(clo).dump_every_bb = (ULong)VG_(atoll)(&arg[16]);
else if (0 == VG_(strcmp)(arg, "--collect-alloc=yes"))
<para><command>Periodic dumping after execution of a specified
number of basic blocks</command>. For this, use the command line
option <option><xref linkend="opt.dump-every-bb"/>=count</option>.
- The resultion of the internal basic block counter of Valgrind is
- only rough, so you should at least specify a interval of 50000
- basic blocks.</para>
+ </para>
</listitem>
<listitem>
<option><![CDATA[--dump-every-bb=<count> [default: 0, never] ]]></option>
</term>
<listitem>
- <para>Dump profile data each <count> basic blocks</para>
+ <para>Dump profile data every <count> basic blocks.
+ Whether a dump is needed is only checked when Valgrinds internal
+ scheduler is run. Therefore, the minimum setting useful is about 100000.
+ The count is a 64-bit value to make long dump periods possible.
+ </para>
</listitem>
</varlistentry>
Bool dump_bbs; /* Dump basic block information? */
/* Dump generation options */
- Int dump_every_bb; /* Dump every xxx BBs. */
+ ULong dump_every_bb; /* Dump every xxx BBs. */
/* Collection options */
Bool separate_threads; /* Separate threads in dump? */
if (CLG_(clo).dump_every_bb >0) {
if (CLG_(stat).bb_executions - bbs_done > CLG_(clo).dump_every_bb) {
- VG_(sprintf)(buf, "--dump-every-bb=%d", CLG_(clo).dump_every_bb);
+ VG_(sprintf)(buf, "--dump-every-bb=%llu", CLG_(clo).dump_every_bb);
CLG_(dump_profile)(buf, False);
bbs_done = CLG_(stat).bb_executions;
}