[Octave-bug-tracker] [bug #44751] Failure to exit when running Octave in --no-gui mode

[Guillaume]

Follow-up Comment #44, bug #44751 (project octave):

Many thanks Dan, seems like you found a solution (with patch 33694)!


./run-octave --no-gui -f -q
LINK> Qt Link Thread Before Move: 35884112
LINK> Qt Link Thread After Move: 38470768
MAIN> JUST CONNECTED confirm_shutdown_signal

>> exit
LINK> octave_qt_link::do_confirm_shutdown thread affinity: 38470768
LINK> LOCKING THE MUTEX
LINK> _shutdown_confirm_result BEFORE EMIT: -1
LINK> EMITTING SIGNAL
MAIN> SLOT IS CALLED: confirm_shutdown_octave
MAIN> main_window::confirm_shutdown_octave thread affinity: 35884112
MAIN> Waiting for link mutex to free...
LINK> _shutdown_confirm_result AFTER EMIT: -1
LINK> GOING INTO WAIT STATE, SIMULTANEOUS UNLOCK MUTEX
MAIN> closenow = 1
MAIN> Attempting to Awake process...
LINK> COMING OUT OF WAIT STATE, shutdown = 1


Given your description, I wonder if it might be linked to the fact that I am
doing the tests from within a VM that has been attributed a single core. It
would also be useful to know if it fixes the problem observed by @andy1978 on
Debian Wheezy.
I'll try your last suggestion later on.

    _______________________________________________________

Reply to this item at:

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

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