Lines Matching full:accesses
44 Memcheck's, but it is able to catch invalid accesses in a number of
49 in <code class="computeroutput">h_main.[ch]</code>, checks accesses
51 <code class="computeroutput">sg_main.[ch]</code>, checks accesses to
60 the likely forms of stack and global array accesses, and, as far as is
112 out of range accesses and accesses to freed memory. The mechanism is
141 <p>Checking of accesses to such arrays would then be relatively
148 if a memory referencing instruction accesses inside a stack or
165 iteration, it accesses somewhere else, possibly a different local,
190 accesses. Memcheck maintains bitmaps telling it which areas of memory
195 freed memory as unaccessible, Memcheck can detect all accesses to
200 fails to detect invalid accesses which just happen to fall within some
215 accesses to blocks freed very far in the past. Memcheck can detect
217 accesses to a freed block, Memcheck must make it inaccessible, hence
221 invalid accesses to them.</p>
223 of four machine words, for detection of accesses to freed blocks. A
225 detect all invalid accesses through any pointers derived from the old
228 accesses in any of the most recently freed 10 million blocks, Ptrcheck
268 subsequent accesses
271 uses that as the "example" of how subsequent accesses should
287 accesses <code class="computeroutput">a[]</code> and
325 accesses to them. This is true even when those arrays are accessed
