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

[John W. Eaton]

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

I am able to reproduce a crash with Ctrl-C if I install OpenBLAS on my system.
 If this is the problem you are seeing, then I think this is a duplicate of
bug #47400.

If you are using OpenBLAS or ATLAS and they are set up to use multiple
threads, can you try uninstalling these libraries and using the reference BLAS
instead?  If that avoids the problem, then I think we can close this as a
duplicate.

If you want to continue debugging, then another thing to try is to enable core
files if the are not already enabled on your system ("ulimit -c unlimited" in
bash) and then run Octave as usual, cause it to crash, then examine the core
file with gdb.  You'll probably need to tell gdb to look at the octave-gui and
the generated core file.  This might be easiest with an installed copy of
Octave instead of trying to run things in the build directory.

    _______________________________________________________

Reply to this item at:

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

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