[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #60490] CTRL+C interrupt does not get intercep
|
From: |
anonymous |
|
Subject: |
[Octave-bug-tracker] [bug #60490] CTRL+C interrupt does not get intercepted during intensive computations |
|
Date: |
Fri, 30 Apr 2021 21:23:29 -0400 (EDT) |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:88.0) Gecko/20100101 Firefox/88.0 |
Follow-up Comment #1, bug #60490 (project octave):
No, the lack of Ctrl-C during computation is itself the feature, which was put
in because there was a bug several years ago of how to handle Ctrl-C when
executing library code. There are many examples in the bug database with
Ctrl-C and multi-threaded code, example here that was labeled "Important":
https://savannah.gnu.org/bugs/index.php?47400
In other words: Ctrl-C will work for Octave's code but when it passes
execution to an external library routine that's multi-threaded, Ctrl-C is
temporarily disabled. This was deemed better than having an interrupt result
in a crash.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60490>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/