[Octave-bug-tracker] [bug #49515] Octave aborts on exit under some conditions with --eval CODE

[Dan Sebald]

Follow-up Comment #3, bug #49515 (project octave):

Oh yeah, I keep forgetting that --no-gui isn't the same as --no-gui-libs.

So more delay (a breakpoint) avoids the problem?  That rules out my
hypothesis.

Quoting:

"the octave-gui executable's main function has already returned and cleaned up
its state."

there is this hunk


  if (! octave_link::confirm_shutdown ())
    return ovl ();


which is supposed to confirm that the GUI is OK to shutdown.  Quoting:

"octave::interpreter::execute function is still running on a QThread"

so this QThread is part of the GUI?  Or just a mechanism that the core is
using to create another thread?  I seems to me that all of this should be
under the confirm_shutdown() umbrella.

    _______________________________________________________

Reply to this item at:

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

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