#14894: Fix PARI error handling (needed for future upgrade to PARI 2.6)
--------------------------------------+------------------------------
Reporter: vbraun | Owner: jdemeyer
Type: defect | Status: needs_work
Priority: major | Milestone: sage-5.12
Component: packages: standard | Resolution:
Keywords: pari error signal | Merged in:
Authors: Peter Bruin | Reviewers: Jeroen Demeyer
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: #12142, #14873 | Stopgaps:
--------------------------------------+------------------------------
Comment (by pbruin):
Replying to [comment:30 jdemeyer]:
> Replying to [comment:29 pbruin]:
> > Of course, for signal handling you are stuck with the slow version
> False :-) Sage's `sig_on()` uses `sigsetjmp(env,0)`. It manually resets
the signal mask when actually handling an error.
OK, I read the code too carelessly. But if you can simply use
`sigsetjmp(env, 0)` for signal handling, then surely you can use it for
handling PARI errors as well, so the slowness of `setjmp()` on BSD should
be irrelevant. The try/catch macros provided by PARI do use a plain
`setjmp()`, but that should be easy to change.
Anyway, if a non-`setjmp()`-based approach is feasible, that would be
great. It would probably still be quite non-trivial, though.
--
Ticket URL: <http://trac.sagemath.org/ticket/14894#comment:32>
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.
