Lines Matching full:errors
18 <para>Helgrind is a Valgrind tool for detecting synchronisation errors
28 <para>Helgrind can detect three classes of errors, which are discussed
90 <title>Detected errors: Misuses of the POSIX pthreads API</title>
94 these are unglamourous errors, their presence can lead to undefined
95 program behaviour and hard-to-find bugs later on. The detected errors
143 <para>Reported errors always contain a primary stack trace indicating
145 traces giving additional information. In particular, most errors
175 <title>Detected errors: Inconsistent Lock Orderings</title>
271 <title>Detected errors: Data Races</title>
726 errors. It will be more effective if you design threaded programs
728 same is true for finding memory errors with Memcheck, but applies more
731 reports (threading) errors than it is to write a correct program for
732 which Memcheck falsely reports (memory) errors.</para>
735 for getting reliable results and avoiding false errors. The first two
737 of false data-race errors.</para>
1019 <para>Helgrind attempts to hide these errors using the standard
1029 observes large numbers of (false) errors in there. Valgrind's
1033 <para>If you see any race errors reported
1087 of lock order errors reported can become annoying, particularly
1088 if you're only interested in race errors. You may therefore find
1151 Helgrind is showing race errors with only one stack instead of
1210 taken into account when removing duplicates of race errors.
1212 identical race errors will be considered to be the same if
1308 <listitem><para>For lock order errors, print the complete lock
1325 for errors, when a "try"-style lock operation happens (e.g.
1330 generate false lock-order errors and confuse users.</para>
