[Octave-bug-tracker] [bug #59628] Segmentation fault on GUI close

[Lars Kindermann]

Follow-up Comment #4, bug #59628 (project octave):

maybe this helps in locating the bug, it can be triggered by command line
parameters only:

while

$ for i in {1..10}; do octave --gui --eval "1+1"; done
$

is always ok, but forcing exit from within octave

$ for i in {1..10}; do octave --gui --eval "1+1,exit"; done
octave exited with signal 11
octave exited with signal 11
octave exited with signal 11
octave exited with signal 11
octave exited with signal 11
octave exited with signal 11
octave exited with signal 11
octave exited with signal 11
$

often crashes on my system, both in todays stable and dev but not in 5.2

Another observation: Even when the signal 11 message is emitted, the return
code of the octave command is still zero. So main seems to exit fine, and the
problem is in a thread?

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59628>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/