[PATCH] D26809: [lli] Handle SIGSEGV in Jit'ed code more gracefully.

[Davide Italiano via llvm-commits]

On Thu, Nov 17, 2016 at 12:28 PM, Filipe Cabecinhas <filcab at gmail.com> wrote:
> What happens if the process wants to handle SIGSEGV?
> You can't say it's in JITted code on the handler, as the signal might come
> from other parts of code, no?
>

As the only pieces of code we're interested into are the RunFunction()
bits, we can (maybe) move this logic to ExecutionEngine or delete the
signal handler via SIG_DFL after runFunction() is executed. How does
that feel?