title: Can undefined behavior erase the hard drive?
body: <p>From "Effective C++ 3rd edition by Scott Meyers":</p>
  
  <blockquote>
    <p>To emphasize that the results of undefined behavior are not predictable and may be very unpleasant, experienced C++ programmers often say that programs with undefined behavior can erase your hard drive.</p>
  </blockquote>
  
  <p>Under what circumstances can this happen? </p>
  
  <p>For example, can accessing and writing to locations out of array range corrupt memory that doesn't belong to this C++ program or thread?</p>