[Top][All Lists]

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

[Octave-bug-tracker] [bug #54444] Octave CLI doesn't terminate at sigter

From: Olaf Till
Subject: [Octave-bug-tracker] [bug #54444] Octave CLI doesn't terminate at sigterm until <ENTER> pressed at prompt
Date: Sat, 2 Mar 2019 15:02:59 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

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

According to current libinterp/corefcn/sighandlers.cc, this seems to be due to
a deliberate change -- signals for which the default action is to terminate
the program are now handled by generic_sig_handler(), meaning that terminating
the program is delayed until respond_to_pending_signals() is called, which
again is only called by octave_quit().

I think this change is problematic. In a resting Octave instance,
octave_quit() is not called. So now it is not possible any more to kill a
resting Octave instance 'from outside', except with a fatal signal for which
the Octave instance can't perform any clean-up actions.

The necessity for killing a resting Octave instance 'from outside', while
still enabling clean-up, is given for Octave servers of the 'parallel'
package. But I think it is also a generally desirable feature.

@jwe: What should be done here?


Reply to this item at:


  Message sent via Savannah

reply via email to

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