[Octave-bug-tracker] [bug #47400] panic on Ctrl+c with multithreaded ATLAS or OpenBLAS

[Lachlan Andrew]

Follow-up Comment #8, bug #47400 (project octave):

Thanks for the test script, Rik.

I notice that when I run this under gdb, I don't get a segfault.  Instead, the
system stops with SIGINT received by the BLAS thread (often in
dgemm_kernel_SANDYBRIDGE).

The very first time, I did get the segfault, and it seemed that the call stack
had been overwritten, since the "real" functions were in fairly high
locations, whereas several had locations like 000000100.

>From the previous comments, I assume that the natural approach is:
1. Ensure that only the octave core thread receives ctrl-C (ensure SIGINT is
masked off when the BLAS is started)
2. Make sure that the cleanup doesn't invalidate any of the data being
operated on by the worker threads, until they can be stopped.

Is that right?

    _______________________________________________________

Reply to this item at:

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

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