https://utcc.utoronto.ca/~cks/space/blog/programming/GoTimeParsingTZIssue #go #bug #api
呃,Go 怎么一堆这种 unexpected behaviour……
呃,Go 怎么一堆这种 unexpected behaviour……
https://www.vidarholen.net/contents/blog/?p=878 #shell #unix #terminal
Zsh and Fish’s simple but clever trick for highlighting missing linefeeds
Zsh and Fish’s simple but clever trick for highlighting missing linefeeds
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
「On Linux it is totally possible to catch and handle SIGSEGV. With that fix, my code will never again crash. For sure.」——233
The 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?
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?