13 Jun
2016
13 Jun
'16
10 p.m.
My argument is _exactly_ that you're _not_ screwed if you accessed something in a mmaped area that didn't behave as you wanted.
And we're discussing mmap()ed areas.
Since Pike has very few ways of screwing up that you would get a SIGSEGV without using mmap I believe it would be a useful function to have.
The only other case for SIGSEGV would be to crash your program to restart it because _Pike itself_ had a bug. I haven't seen that case for many years. YMMV.
(I have gotten SIGILL because the CPU screwed up, but not SIGSEGV.)