Lines Matching full:accesses
23 Memcheck's, but it is able to catch invalid accesses in a number of
29 in <computeroutput>h_main.[ch]</computeroutput>, checks accesses
31 <computeroutput>sg_main.[ch]</computeroutput>, checks accesses to
41 the likely forms of stack and global array accesses, and, as far as is
110 out of range accesses and accesses to freed memory. The mechanism is
148 <para>Checking of accesses to such arrays would then be relatively
155 if a memory referencing instruction accesses inside a stack or
174 iteration, it accesses somewhere else, possibly a different local,
209 accesses. Memcheck maintains bitmaps telling it which areas of memory
214 freed memory as unaccessible, Memcheck can detect all accesses to
220 fails to detect invalid accesses which just happen to fall within some
238 accesses to blocks freed very far in the past. Memcheck can detect
240 accesses to a freed block, Memcheck must make it inaccessible, hence
244 invalid accesses to them.</para>
247 of four machine words, for detection of accesses to freed blocks. A
249 detect all invalid accesses through any pointers derived from the old
252 accesses in any of the most recently freed 10 million blocks, Ptrcheck
314 subsequent accesses by that instruction, until the containing function
317 uses that as the "example" of how subsequent accesses should
337 accesses <computeroutput>a[]</computeroutput> and
384 accesses to them. This is true even when those arrays are accessed
