[PATCH 0/2] Fix SIGSEGV handler and other synchronous signals
dshea at redhat.com
Mon Sep 15 13:27:44 UTC 2014
On 09/15/2014 02:24 AM, Vratislav Podzimek wrote:
> On Fri, 2014-09-12 at 16:12 -0400, Chris Lumens wrote:
>>> Ever noticed that the SIGSEGV handler never actually gets called?
>> Now that you mention it, yeah. I was curious what was happening there.
> I've seen it being called, resulting in a nother SIGSEGV. :)
> Looks good to me as well.
Oh wow, really? In light of that, I think it'd be a good idea to undo
the part where I took out
- signal(SIGSEGV, SIG_DFL); /* back to default */
Since if we keep that in, a crash in the signal handler will just crash anaconda all the way instead of getting stuck in a signal handler loop. And I guess I should add a comment to that effect.
More information about the anaconda-patches