Lines Matching full:race
278 <para>A data race happens, or could happen, when two threads access a
282 are race-free is one of the central difficulties of threaded
290 <sect2 id="hg-manual.data-races.example" xreflabel="Simple Race">
291 <title>A Simple Data Race</title>
293 <para>About the simplest possible example of a race is as follows. In
335 Possible data race during read of size 4 at 0x601038 by thread #1
351 The last clause is the main error message. It says there is a race as
362 definition, a race involves two different threads accessing the
367 data race during read of size 4 ...</computeroutput>" and the
370 usually able to show both accesses involved in a race. At least
396 <para>The following section explains Helgrind's race detection
404 <title>Helgrind's Race Detection Algorithm</title>
443 considered buggy (it has a race) because the final value
486 And so there is no longer a race
500 that's fine; if not, it reports a race.</para>
584 to the other, then it reports a race.</para>
589 <listitem><para>Helgrind doesn't check for a race in the case where
608 <sect2 id="hg-manual.data-races.errmsgs" xreflabel="Race Error Messages">
609 <title>Interpreting Race Error Messages</title>
611 <para>Helgrind's race detection algorithm collects a lot of
612 information, and tries to present it in a helpful way when a race is
630 Possible data race during read of size 4 at 0x601070 by thread #3
655 "<computeroutput>Possible data race during read</computeroutput>". At
680 cause of the race?</para>
707 The fact that Helgrind is reporting a race means it did not observe
742 of false data-race errors.</para>
923 discussed at length by Arndt Muehlenfeld ("Runtime Race Detection
976 helgrind might report false positive race conditions on these
977 variables, despite being very probably race free. On Linux, you can
1032 generates many false race reports when you use these functions.</para>
1048 <para>If you see any race errors reported
1103 if you're only interested in race errors. You may therefore find
1117 it can produce two stack traces in a race report -- both the
1129 of a previously race-free program.</para>
1166 Helgrind is showing race errors with only one stack instead of
1212 types of race conditions in the application would not be reported.
1231 that is race reporting is suppressed there. DRD does the same thing
1262 <varlistentry id="opt.cmp-race-err-addrs"
1263 xreflabel="- -cmp-race-err-addrs">
1265 <option><![CDATA[- -cmp-race-err-addrs=no|yes [no]
1269 <para>Controls whether or not race (data) addresses should be
1270 taken into account when removing duplicates of race errors.
1271 With <varname>- -cmp-race-err-addrs=no</varname>, two otherwise
1272 identical race errors will be considered to be the same if
1273 their race addresses differ. With
1274 With <varname>- -cmp-race-err-addrs=yes</varname> they will be
