Re: System.Memory and mmap()

Mirar @ Pike developers forum wrote:

Does Pike have any functionality to catch segfaults and similar errors that might be caused by a bad mmap?

I don't think I've ever encountered a C-program that did anything meaningful after catching a SIGSEGV. In most cases, trying to catch that and recovering is a bad idea. That signal usually belongs to debuggers and stacktraces.

Once a Pike program triggers a SIGSEGV due to a bad mmap, you need to fix your mmap usage. This inevitably needs to be done during the development stage. This usually is not something that can be handled satisfactory while in a production environment with mere users around.