#13882: Deal with a trivial case in dlx_solver
-----------------------------------------+----------------------------------
       Reporter:  SimonKing              |         Owner:  sage-combinat
           Type:  defect                 |        Status:  needs_review 
       Priority:  major                  |     Milestone:  sage-5.6     
      Component:  combinatorics          |    Resolution:               
       Keywords:  dlx_solver nr_columns  |   Work issues:               
Report Upstream:  N/A                    |     Reviewers:               
        Authors:  Simon King             |     Merged in:               
   Dependencies:                         |      Stopgaps:               
-----------------------------------------+----------------------------------

Comment (by SimonKing):

 Replying to [comment:4 fbissey]:
 > With your change the following in combinat/tiling.py will have to be
 changed
 > {{{
 >                 sage: from sage.combinat.matrices.dancing_links import
 dlx_solver
 >                 sage: rows = []
 >                 sage: x = dlx_solver(rows)
 >                 sage: x.search()        # not tested
 >                 BOOM !!!
 > }}}

 Why? It still goes "BOOM". Actually, the fix from here is responsible for
 the fact that in the debug version the line `x = dlx_solver(rows)` does
 not crash. But the segfault in `x.search()` will still occur.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13882#comment:5>
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.

Reply via email to