Lines Matching full:stack
8 xreflabel="SGCheck: an experimental stack and global array overrun detector">
9 <title>SGCheck: an experimental stack and global array overrun detector</title>
21 <para>SGCheck is a tool for finding overruns of stack and global
23 observation about the likely forms of stack and global array accesses.
53 debugging information which describes the location of all stack and
63 if a memory referencing instruction accesses inside a stack or
77 of <computeroutput>a[]</computeroutput> on the stack, and so we can
83 possibly an un-accounted for area of the stack (eg, spill slot), so
91 copying loop only ever access one particular stack or global variable, we
115 created by heap or stack allocations. But it does not perform bounds
116 checking for stack or global arrays.</para>
118 <para>SGCheck, on the other hand, does do bounds checking for stack or
142 stack or global array creates an association between that
197 stack and global checks can sometimes require a number of range
205 <para>Coverage: Stack and global checking is fragile. If a shared
207 not be able to determine the bounds of any stack or global arrays
215 silently skip stack and global checking for such objects. It would
221 or written by system calls do overrun stack or global arrays. This
226 <para>Platforms: the stack/global checks won't work properly on
228 That's because the stack and global checking requires tracking
237 even in the presence of longjmps within the same stack (although
256 <para>Extend system call checking to work on stack and global arrays.</para>
268 transition from a heap to a stack object almost certainly isn't a
297 <para> sg_main.c: Improve the performance of the stack / global
299 areas which "obviously" can't be stack or globals. This will
