SignalHandling returns from SEGFAULT signal handler

[danielk]

If you return from a SIGFAULT, SIGFPE, SIGBUS, or SIGILL the offending code is re-run and the signal is raised again.

If the fault occurs in the the UI thread where SignalHandler::handleSignal() is run in it will never run since we never get the opportunity to continue on to where the QSocketNotifier events are handled.

This leads the write() in SignalHandler::signalHandler() to block forever, deadlocking the UI thread.

[danielk]

Proof-of-concept fix.

[Daniel Thor Kristjansson <danielk@…>]

In 546fdac8d1e952422c91278be3187ae87aded28e/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[Daniel Thor Kristjansson <danielk@…>]

In 6f218b1ab4ad067f564eb07919560970cbb77de2/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[Daniel Thor Kristjansson <danielk@…>]

In 62f3c643d80e617aa718421795ca3ac216e3c7cc/mythtv:

Error: Processor CommitTicketReference failed

GIT backend not available

[beirdo]

I think what you have so far will work, but I'm considering restructuring it so the signal handlers are in their own thread, which should simplify things a bit. If this hasn't been changed by Aug 1, please remind me to close it as fixed :)

[beirdo]

This is well past Aug 1, 2012. Let's consider this fixed.