Editing Valgrind (section)

==Limitations of Memcheck==
In addition to the performance penalty, an important limitation of Memcheck is its inability to detect all cases of bounds errors in the use of static or stack-allocated data.<ref>[http://www.valgrind.org/docs/manual/faq.html#faq.overruns Valgrind FAQ]</ref> The following code will pass the ''Memcheck'' tool in Valgrind without incident, despite containing the errors described in the comments:

<syntaxhighlight lang="c">
  int Static[5];
  
  int func(void)
  {
    int Stack[5];
  
    Static[5] = 0;  /* Error - Static[0] to Static[4] exist, Static[5] is out of bounds */
    Stack [5] = 0;  /* Error - Stack[0] to Stack[4] exist, Stack[5] is out of bounds */
    
    return 0;
  }
</syntaxhighlight>



The inability to detect all errors involving the access of stack allocated data is especially noteworthy since
[[Buffer overflow|certain types of stack errors]] make software [[Vulnerability (computing)|vulnerable]] to the classic
[[Stack buffer overflow|stack smashing exploit]].