News for hackers. Stuff that matters.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by fanf2 on Thursday June 18, 2020 @09:18AM (#23562794)
The original Bourne shell trapped SEGV (which it called MEMF) as part of its memory management strategy - https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/cmd...
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by chrisseaton on Thursday June 18, 2020 @09:48AM (#23563055)
Almost all language runtimes trap SEGV for memory management and other services.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by jeffffff on Thursday June 18, 2020 @09:33AM (#23562934)
most modern concurrent copying garbage collectors use memory protection and sigsegv handlers to avoid the need for locking