[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53953] CTRL+C is not passed to working script

From: anonymous
Subject: [Octave-bug-tracker] [bug #53953] CTRL+C is not passed to working script environment
Date: Wed, 6 Jun 2018 22:05:27 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #5, bug #53953 (project octave):

Well, I am not sure, is it the same. But I upgraded from 4.2.2 to 4.4.0, so I
do not know how that was in 4.3.

>From my perspective, the difference is that CTRL+C has absolutely normal
effect on the script itself, but it is not passed to the environment of child
processes, like external solvers (Windows executables).

I am using OpenEMS solver. In the past, I was stopping it with CTRL+C from GUI
console by demand, when it was going wrong way. Now I have to kill the process
unsafely, which can bring undesired impact on the system.

Considering __run_test_suite__, I confirm, it is passed and can be terminated
with CTRL+C during any test, and not between tests only. But with some minimal
delay (about 1/3-1/2 sec).
May I guess? Can this delay be related to problems of passing event messages
between processes? So in case of external computational binary, the messages
are delayed infinitely?

So, probably, it can be the same problem as in the bug #53635.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]