[Octave-bug-tracker] [bug #51886] Ctrl-C crash is back

[Lars Kindermann]

Follow-up Comment #6, bug #51886 (project octave):

Uninstalling OpenBLAS solved the problem indeed.

However, I checked the SIGINT handling again and found:

Without OpenBlas exactly two SIGINTs are sent to QTthred after Ctrl-C

With OpenBlas infinitely many are sent to QTthread and lt-octave-gui. That
sounds pretty insane.

If the problem is due to Octave, I can imagine two scenarios:

The SIGINTs are sent in a loop or callback to the apropriate threads after a
Ctrl-C is caught, but the code does not remember that it has been done already
and continues to do forever. That might be easy to fix.

Or the many SIGINTS are by design because it is difficult to stop all the
multipe threads. But even then it might be possible to limit the number and/or
rate do avoid crashes.

Maybe this way the Ctrl-C problem with multithreaded BLAS / ATLAS libs can be
solved. Sorry, I'm not very literate in C/C++ but if you point me to the
relevant piece of code I can try to have a look.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51886>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/