> So if a program segfaults on me and I don't know exactly why, I should dial my paranoia up and expect that it is insecure. This is true in that the program c

> So if a program segfaults on me and I don't know exactly why, I should dial my paranoia up and expect that it is insecure. This is true in that the program contains at least one bug, but some memory errors are safer than others. A SIGBUS is safer than SIGSEGV (usually means you mmapped a file and got an I/O error reading it) and a read is safer than a write. This comes up if you're prioritizing crashes from fuzzing.