#11814: Segmentation fault in dlx_solver
-------------------------+-------------------------------------------------
Reporter: | Owner: sage-combinat
jdemeyer | Status: new
Type: | Milestone: sage-6.4
defect | Resolution:
Priority: | Merged in:
critical | Reviewers:
Component: | Work issues:
combinatorics | Commit:
Keywords: | 25741dfc1c52709faa59042024248824247275f4
Authors: | Stopgaps:
Report Upstream: N/A |
Branch: |
u/slabbe/11814 |
Dependencies: |
-------------------------+-------------------------------------------------
Comment (by jdemeyer):
Replying to [comment:10 slabbe]:
> I just pushed a branch (based on 6.6.rc2) where the segmentation fault
is catch using sig_on and sig_off.
>
> Do we want to also solve the segmentation fault itself in this ticket?
First of all, I would absolutely never doctest segfaults unless you know
that it's safe to do so.
I don't mind just adding the `sig_on`/`sig_off` in this ticket provided
that you create a new ticket for the segmentation fault itself.
--
Ticket URL: <http://trac.sagemath.org/ticket/11814#comment:12>
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/d/optout.
