Lines Matching full:accesses
57 accesses via locking. E.g. the POSIX threads library, the Qt library
157 Which source code statements generate which memory accesses depends on
269 conflicting memory accesses are ordered by synchronization
287 many conflicting memory accesses in such applications and although such
295 algorithm is to verify whether all shared memory accesses follow a consistent
297 whether all interthread memory accesses are ordered by synchronization
373 memory accesses that occur after memory has been freed but might cause
597 There are always at least two memory accesses involved in a data
598 race. Memory accesses involved in a data race are called
599 <emphasis>conflicting memory accesses</emphasis>. DRD prints a
688 A conflicting access involves at least two memory accesses. For
689 one of these accesses an exact call stack is displayed, and for
690 the other accesses an approximate call stack is displayed,
692 accesses. This information can be interpreted as follows:
955 source code statements triggered the conflicting accesses, it can be
994 DRD about the order of inter-thread memory accesses implemented via
1137 DRD to ignore all memory accesses performed by the current thread.
1143 DRD to stop ignoring the memory accesses performed by the current thread.
