On 2019-05-27 16:11, Tracy Hall wrote:
in particular it seems to have undefined behavior in subsequent calls after it has been interrupted by alarm().
This is simply a fact of life and not really considered to be a bug. You should not rely on the fact that interruptions (using either CTRL-C or alarm) work perfectly. Don't use alarm() for serious computations.
If you need proper timeouts, one thing you can do is spawn multiple Sage processes or fork one Sage process. Then you can kill the whole process after a certain amount of time.
-- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-support/5CEC0B7F.3060503%40UGent.be. For more options, visit https://groups.google.com/d/optout.
