Re: interrupt handing and the GUI (bug #37672)

[Michael Goffioul]

On Mon, Nov 11, 2013 at 1:35 AM, John W. Eaton <address@hidden> wrote:

On 11/10/2013 10:45 PM, Daniel J Sebald wrote:

The last answer at this link seems to know more than the rest of us:

http://stackoverflow.com/questions/12820765/can-i-send-signals-to-different-threads

Maybe there is something there.

Yes, it mentions pthread_kill.  That appears to allow us to direct a
signal to a particular thread.

I'm attaching a patch that seems to at least partially work for me.
At least interrupts seem to work now inside sleep and long running
functions like "inv (large_matrix)", but now I also get random
segfaults when typing Ctrl-C in the command window after a few
interrupts have been processed (it seems random).

Does it make any difference if you block the SIGINT signal in the GUI thread with pthread_sigmask and continue using raise? 

 

I don't expect it will work on Windows.  I suppose it just
happens to work for me because Qt is using pthreads on my system.
What if Qt doesn't use pthreads?

I wouldn't bother too much about Windows here, as SIGINT handling is quite different and AFAIK *always* happen in a separate thread just created by the OS to handle the signal.

Michael.