Thank god you did not. Catching SIGSEGV and attempting corrective action is among the worst kinds of hubris that one can attempt. Eh? You don't like the original Bourne shell's assumption of `got a SEGV; must need more memory, so let's sbrk() some more'?