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

[Mike Miller]

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

That is not a safe assumption. Specifically, when running octave (or the
octave-gui executable directly), the --eval option implies the same thing as
the --no-gui option (unless the --force-gui or --persist options are also
given).

If you actually meant octave-cli (or octave --no-gui-libs), then yes you are
correct, this problem does not occur under the octave-cli executable.

Could be, might be, either one of those things.

It is odd that if I set a gdb breakpoint on or inside the octave_qt_link
destructor, the error does not occur.

If I get rid of the explicit call to `exit()`, the error changes from a
SIGABRT (due to a pure virtual method being called) to a SIGSEGV, but with the
same general state: the octave::interpreter::execute function is still running
on a QThread while the octave-gui executable's main function has already
returned and cleaned up its state.

    _______________________________________________________

Reply to this item at:

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

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