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

[Guillaume]

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

And I get this:


./run-octave --no-gui -f -q

POINTER: _octave_qt_link = 23606832
JUST CONNECTED confirm_shutdown_signal

>> exit
LOCKING THE MUTEX
EMITTING SIGNAL
SLOT IS CALLED: confirm_shutdown_octave
closenow = 1
GOING INTO WAIT STATE, SIMULTANEOUS UNLOCK MUTEX


Something that might be interesting, or not, is what I observed when using the
GUI but having a non-saved file in the editor so that I am asked whether I
want to save it before exiting; I press cancel, save it/close it and type exit
again: I then get block in the same way than with --no-gui:


>> exit
LOCKING THE MUTEX
EMITTING SIGNAL
GOING INTO WAIT STATE, SIMULTANEOUS UNLOCK MUTEX
SLOT IS CALLED: confirm_shutdown_octave   <- Cancel then close/save file ->
closenow = 0
Attempting to Awake process...
COMING OUT OF WAIT STATE, shutdown = 0
>> exit
LOCKING THE MUTEX



    _______________________________________________________

Reply to this item at:

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

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