#11752: ecl.pyx should not touch SIGPWR neither SIGXCPU when initializing ecl
--------------------------+-------------------------------------------------
Reporter: pcpa | Owner: was
Type: defect | Status: new
Priority: major | Milestone: sage-4.7.2
Component: interfaces | Keywords:
Work_issues: | Upstream: N/A
Reviewer: | Author:
Merged: | Dependencies:
--------------------------+-------------------------------------------------
Comment(by nbruin):
Replying to [comment:2 pcpa]:
> The patch allows sage to load the ecl/maxima module and at least the
(few) doctests I run did work correctly.
This does not test asynchronous signal handling at all. The easiest way to
do so is to start up a time-consuming job and send some Ctrl-C signals to
the process (I don't think there are many other async signals Sage is
required to handle properly). See #10818 for some relevant tests and
ideas.
>Patch probably can be made a one liner by just not restoring handlers
after cl_boot call, and for more clarity, use proper signal names, instead
of numeric value.
You'll at least have to restore the SIGINT handler.
> This should at least help in knowing beforehand issues that will happen
in the future if sage is linked to other binaries, multi thread or not,
that use Boehm GC, or do their own signal management.
Absolutely! This is very useful work.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11752#comment:3>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
