Post #22 263 Jun 18, 2020, 13:24 UTC https://blog.cloudflare.com/why-is-there-a-v-in-sigsegv-segmentation-fault/ #unix #c #history「On Linux it is totally possible to catch and handle SIGSEGV. With that fix, my code will never again crash. For sure.」——233 Cloudflare Blog Why is there a "V" in SIGSEGV Segmentation Fault? My program received a SIGSEGV signal and crashed with "Segmentation Fault" message. Where does the "V" come from? Did I read it wrong? Was there a "Segmentation *V*ault?"? Or did Linux authors make a mistake? Shouldn't the signal be named SIGSEGF?