#9640: Change PARI error catching mechanism
----------------------------------------+----------------------------
Reporter: jdemeyer | Owner: was
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.13
Component: interfaces | Resolution:
Keywords: pari error interrupt | Merged in:
Authors: Peter Bruin | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------------+----------------------------
Comment (by pbruin):
Replying to [comment:13 jdemeyer]:
> Instead of using `sage_siglongjmp()`, I think it's safer to call
`abort()` and use the normal signal handling mechanism. Otherwise we have
to consider race conditions like a `SIGINT` arriving during the
`sage_siglongjmp()` call...
Why `abort()` and not `raise(SIGUSR1)` or another signal code?
--
Ticket URL: <http://trac.sagemath.org/ticket/9640#comment:16>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
