#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 pcpa):
I just did a build of ecl.so without patching the code to save/restore
signal handlers and it does still work, so, it is only required the call
to `ecl_set_option()`. As long as there is only one thread, it should be
ok, as Bohem GC for sure will not pthread_kill(pthread_self(),
SIG{PWR,XCPU}), and one should not inject whatever code is required to
create a thread in `ecl_eval()`.
Only testing to see what would happen with multiple threads, what would be
desirable would be to have "a single Bohem GC instance". In one quick test
I did, it failed miserably, that was to link libcsage.so to -lpthread, do
a `s/sigprocmask/pthread_sigmask/` including gc.h and calling `GC_init()`
before setting signal handles in interrupt.c. It did print some weird
messages rooted in the `cl_boot()` call and crashed.
Updating again the patch, that now is only the ecl_set_option call, and
sync to missing ECL_OPT values.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11752#comment:10>
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.
