Viktor Dukhovni:
> Alternatively, we could siglongjmp() out of a segfault handler, enabled
> around PCRE lookups, leaking whatever heap space libpcre may have
> allocated along the way, and log a more informative message, and thereby
> perhaps even avoid occasional service throttling in master that may happen
> if the service is killed by a signal. Just a thought...
After SIGSEGV the only sensible thing a process can do is to
terminate, because the state of memory is undefined.
Are you assuming that you can know exactly why SIGSEGV is received?
I don't think so. We have to assume the worst, namely, that a process
has corrupted it memory.
Wietse
