Lines Matching full:heap
8 xreflabel="Ptrcheck: an experimental heap, stack and global array overrun detector">
9 <title>Ptrcheck: an experimental heap, stack and global array overrun detector</title>
21 <para>Ptrcheck is a tool for finding overruns of heap, stack
30 through heap-derived pointers. The other part, in
37 <para>The heap-check part is an extensively-hacked (largely rewritten)
64 and heap arrays.
66 global array checks are omitted, and only heap checking is
82 loads which partially overlap the end of heap blocks -- that is,
87 same as loads from completely invalid addresses: an illegal heap
105 <sect1 id="pc-manual.how-works.heap-checks"
106 xreflabel="How Ptrcheck Works: Heap Checks">
107 <title>How Ptrcheck Works: Heap Checks</title>
109 <para>Ptrcheck can check for invalid uses of heap pointers, including
115 heap block (if any) it was derived from. Then, when an access is made
208 <para>Memcheck and Ptrcheck use different approaches for checking heap
225 heap blocks. It tracks pointers which are derived directly from calls
234 through a heap-derived pointer, no matter how far from the original
266 further heap, global or stack errors.</para>
286 <para>Heap checks: Ptrcheck can occasionally lose track of, or
287 become confused about, which heap block a given pointer has been
294 <para>Heap checks: Ptrcheck only tracks pointers that are stored
302 <para>Heap checks: Ptrcheck needs to "understand" which system
366 difficulties. The heap-check side is potentially quite fast. The
374 <para>Coverage: the heap checking is relatively robust, requiring
377 and is able to heap-check programs even with no debugging information
396 system calls do not overrun heap blocks. But it doesn't currently
