[Octave-bug-tracker] [bug #49532] parallel package: segmentation fault on matrix multiplication on macOS

[Mike Miller]

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

Have you tried octave-cli instead of "octave --no-gui" when logged in locally
on the machine? They are not the same, "octave --no-gui" still starts a
QApplication and runs the Octave interpreter on a secondary thread.

When you see the message "octave: no graphical display found" and "octave:
disabling GUI features", that means that octave-cli is being run because it is
running in a headless environment.

So again, the problem appears to me to be due to the use of fork in the
parallel package when the interpreter is not the primary thread and it is
running in a Qt context (even without the GUI).

If you have the gdb debugger, you can try running Octave in the way that
causes it to segfault, attach to the process with gdb in a separate terminal,
and then trigger the segfault. See http://wiki.octave.org/Debugging_Octave for
some information on using gdb with Octave.

    _______________________________________________________

Reply to this item at:

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

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