|
From: | Dan Sebald |
Subject: | [Octave-bug-tracker] [bug #49515] Octave aborts on exit under some conditions with --eval CODE |
Date: | Wed, 2 Nov 2016 23:09:20 +0000 (UTC) |
User-agent: | Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:42.0) Gecko/20100101 Firefox/42.0 |
Follow-up Comment #11, bug #49515 (project octave): What you described sounds correct. The handshake is done in the bool octave_qt_link::do_confirm_shutdown (void) { // Lock the mutex before emitting signal. mutex.lock (); emit confirm_shutdown_signal (); // Wait while the GUI shuts down. waitcondition.wait (&mutex); // The GUI has sent a signal and the thread has been awakened. mutex.unlock (); return _shutdown_confirm_result; } call. The GUI thread is responding to confirm_shutdown here: // Wait for link thread to go to sleep state. _octave_qt_link->mutex.lock (); _octave_qt_link->shutdown_confirmation (closenow); _octave_qt_link->mutex.unlock (); // Awake the worker thread so that it continues shutting down (or not). _octave_qt_link->waitcondition.wakeAll (); So there is a sleep/awake happening, but it is supposed to be before reaching this octave_sleep (86400); line. So I don't know what is waking the core once it gets to this line. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?49515> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |