|
From: | Guillaume |
Subject: | [Octave-bug-tracker] [bug #44751] Failure to exit when running Octave in --no-gui mode |
Date: | Thu, 16 Apr 2015 18:19:18 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0 |
Follow-up Comment #41, bug #44751 (project octave): It did exit indeed :-) but there was no delay. ./run-octave --no-gui -f -q Qt Link Thread Before Move: 33762384 Qt Link Thread After Move: 36349040 JUST CONNECTED confirm_shutdown_signal >> exit octave_qt_link::do_confirm_shutdown thread affinity: 36349040 LOCKING THE MUTEX _shutdown_confirm_result BEFORE EMIT: -1 EMITTING SIGNAL SLOT IS CALLED: confirm_shutdown_octave main_window::confirm_shutdown_octave thread affinity: 33762384 closenow = 1 _shutdown_confirm_result AFTER EMIT: -1 GOING INTO WAIT STATE, SIMULTANEOUS UNLOCK MUTEX WAS THERE A 3 SECOND BEFORE THIS LINE APPEARED???? Couldn't get lock, bad handshake COMING OUT OF WAIT STATE, shutdown = 1 _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?44751> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |