conflicting access information is stored. If you find that
Helgrind is showing race errors with only one stack instead of
the expected two stacks, try increasing this value.</para>
- <para>The minimum value is 10,000 and the maximum is 10,000,000
- (ten times the default value). Increasing the value by 1
+ <para>The minimum value is 10,000 and the maximum is 20,000,000
+ (twenty times the default value). Increasing the value by 1
increases Helgrind's memory requirement by very roughly 100
- bytes, so the maximum value will easily eat up an extra
- gigabyte or so of memory.</para>
+ bytes, so the maximum value will easily eat up two extra
+ gigabytes or so of memory.</para>
</listitem>
</varlistentry>
else if VG_XACT_CLO(arg, "--history-level=full",
HG_(clo_history_level), 2);
- /* If you change the 10k/10mill limits, remember to also change
+ /* If you change the 10k/20mill limits, remember to also change
them in assertions at the top of event_map_maybe_GC. */
else if VG_BINT_CLO(arg, "--conflict-cache-size",
- HG_(clo_conflict_cache_size), 10*1000, 10*1000*1000) {}
+ HG_(clo_conflict_cache_size), 10*1000, 20*1000*1000) {}
/* "stuvwx" --> stuvwx (binary) */
else if VG_STR_CLO(arg, "--hg-sanity-flags", tmp_str) {
/* Check for sane command line params. Limit values must match
those in hg_process_cmd_line_option. */
tl_assert( HG_(clo_conflict_cache_size) >= 10*1000 );
- tl_assert( HG_(clo_conflict_cache_size) <= 10*1000*1000 );
+ tl_assert( HG_(clo_conflict_cache_size) <= 20*1000*1000 );
/* Check our counting is sane (expensive) */
if (CHECK_CEM)