title: Segfaulting only without valgrind
body: <p>I get my final "done" message with valgrind, and get this exit report:</p>
  
  <pre><code>==3434== HEAP SUMMARY:
  ==3434==     in use at exit: 8,432 bytes in 4 blocks
  ==3434==   total heap usage: 4,369 allocs, 8,037 frees, 377,356 bytes allocated
  ==3434== 
  ==3434== LEAK SUMMARY:
  ==3434==    definitely lost: 152 bytes in 1 blocks
  ==3434==    indirectly lost: 0 bytes in 0 blocks
  ==3434==      possibly lost: 0 bytes in 0 blocks
  ==3434==    still reachable: 8,192 bytes in 2 blocks
  ==3434==         suppressed: 88 bytes in 1 blocks
  ==3434== Rerun with --leak-check=full to see details of leaked memory
  ==3434== 
  ==3434== For counts of detected and suppressed errors, rerun with: -v
  ==3434== ERROR SUMMARY: 100190 errors from 140 contexts (suppressed: 0 from 0)
  </code></pre>
  
  <p>But when I run it without valgrind, it segfaults immediately. Does valgrind suppress a certain kind of error that I should be looking for? I can't find any information about this online</p>