#13437: Clean up SIGALRM handling in p_iter_fork
-------------------------------+--------------------------------------------
Reporter: nbruin | Owner: tbd
Type: defect | Status: new
Priority: minor | Milestone: sage-5.4
Component: performance | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: | Merged in:
Dependencies: | Stopgaps:
-------------------------------+--------------------------------------------
Comment (by nbruin):
That's not too surprising. A SEGV is quite different from an EINTR and
with what we know now, it is not so far fetched that under GDB's control,
the occurrence of EINTRs is a little different. I think there is merit to
the proposed patch here for general reasons.
For your SEGV problem: just dig into sage-doctest and extract the ....py
file that gets run to test the doctests. That likely still triggers the
SEGV and then you can run that file under other controls and/or with
instrumentation. At least it'll get the doctest pipes out of your way.
It's also a good way to see that doctests are run in a different
environment than interactive sage use.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13437#comment:4>
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.
