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

[Dan Sebald]

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

Here is another diff file for you to try.  All I've added over the previous
diff is a


  // Move this link object in the same thread as the interpreter.
  moveToThread (main_thread);


[Note: "main_thread" here does not mean the main program thread.  A better
name might have been "interpreter_thread".]

This is meant to test the theory that signals are direct rather than queued
because the Qt link is constructed under the main program thread.

The main_window needs to be in the main program thread, and that is
constructed in octave-gui.cc.  The interpreter is in a worker thread created
by the Qt link.  However, in the repository the Qt link is constructed by
main_window (main thread).  In the patch here:

https://savannah.gnu.org/bugs/download.php?file_id=33550

the Qt link is constructed prior to the main_window, but that still is
instantiated by the main thread in octave-gui.cc.

So, let's see if it is possible to explicitly move the Qt link to the other
thread and thereby make the signals it emits queued.

(file #33625)
    _______________________________________________________

Additional Item Attachment:

File name: move_qtlink_thread-2015apr09.diff Size:2 KB


    _______________________________________________________

Reply to this item at:

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

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