|
From: | Michael Goffioul |
Subject: | [Octave-bug-tracker] [bug #40689] MinGW: octave-3.7.7+.exe process keeps running after GUI starts |
Date: | Sun, 24 Nov 2013 16:57:03 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.57 Safari/537.36 |
Follow-up Comment #2, bug #40689 (project octave): I think this is a result of this changeset: http://hg.savannah.gnu.org/hgweb/octave/rev/1329866151be The problem this changeset is solving is to keep the octave "wrapper" process active while the child process (CLI of GUI) is running. And this is exactly what you're seeing. The wrapper process is the one executing in the cmd32.exe window. I believe this changeset is still required. Without it, the wrapper will exit as soon as the child process starts (the child process running in a "detached" mode). This makes it impossible to use run-octave with the expected bevahior. Or calling "octave" in a shell/batch script: something like "octave -q --eval 'my_long_function()'" will exit before my_long_function is actually executed. I think a simple workaround to avoid having the pending cmd32.exe window is to call octave-gui directly, instead of using the octave wrapper executable. _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?40689> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |