[Octave-bug-tracker] [bug #47400] Repeatable panic on ctrl-c

[anonymous]

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

I poked around more with gdb. My ATLAS installation creates a thread per
processor core and does what looks like a 40x40 submatrix multiplication (the
40 must have been what it decided was optimal at ATLAS build time). On hitting
ctrl-c, only the Octave parser responds but the background ATLAS threads are
all still running. I don't see yet why this should cause an Octave panic
instead of the OS just harvesting the orphan threads quietly.

One workaround we can try is temporarily disabling ctrl-c or SIGINT if the
matrix or exponent passed to mpower are sufficiently large. That may surprise
the user a little if they want to halt, but will be less astonishing than
losing the session to a panic. It also will be independent of the BLAS
implementation. Thoughts?


    _______________________________________________________

Reply to this item at:

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

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