title: Does a stack overflow always lead to a segmentation fault error?
body: <p>In Linux, when a running program attempts to use more stack space than the limit (a stack overflow), that usually results in a "segmentation fault" error and the execution is aborted.</p>
  
  <p>Is it guaranteed that exceeding the stack space limit will always cause a segmentation fault error? Or could it happen that the program continues to run, possibly with some erroneous behavior due to data having been corrupted?</p>
  
  <p>Another way of putting this: if a program misbehaves by producing wrong results but without a crash, can the cause still be a stack overflow?</p>
  
  <p>Edit: to clarify, this question is not about "stack buffer overflow", it is about stack overflow, when the stack space used by the program exceeds the stack size limit (the limit that is in Linux given by <code>ulimit -s</code>).</p>