#10797: update PolyBoRi to newest upstream release 0.7
-----------------------------------------------+----------------------------
   Reporter:  malb                             |       Owner:  AlexanderDreyer
       Type:  enhancement                      |      Status:  needs_work     
   Priority:  major                            |   Milestone:  sage-4.7       
  Component:  packages                         |    Keywords:  polybori       
     Author:  Martin Albrecht,AlexanderDreyer  |    Upstream:  N/A            
   Reviewer:  Martin Albrecht                  |      Merged:                 
Work_issues:                                   |  
-----------------------------------------------+----------------------------
Changes (by malb):

  * status:  positive_review => needs_work


Comment:

 Hi,

 it seems I found a regression in the PolyBoRi 0.7.0 update:

 {{{
 #!python
 sage: B.<a,b,c,d,e,f> = BooleanPolynomialRing()
 sage: F = Ideal(B.random_element() for _ in range(B.ngens()))
 sage: F
 Ideal (a*b + a + b*e + c*e + 1, a + b + c*d + c + 1, a*c + c + d*f + d +
 1, a*c + c*f + c + d*f + 1, c*f + c + d + e + 1, a + b*c + b*d + e*f + 1)
 of Boolean PolynomialRing in a, b, c, d, e, f
 sage: F.groebner_basis()

 ------------------------------------------------------------
 Unhandled SIGSEGV: A segmentation fault occurred in Sage.
 This probably occurred because a *compiled* component
 of Sage has a bug in it (typically accessing invalid memory)
 and is not properly wrapped with sig_on(), sig_off().
 You might want to run Sage under gdb with 'sage -gdb' to debug this.
 Sage will now terminate (sorry).
 ------------------------------------------------------------
 }}}

 '''Backtrace'''

 {{{
 Program received signal SIGSEGV, Segmentation fault.
 [Switching to Thread 0x7f192e07c6e0 (LWP 13588)]
 linalg_step_modified (polys=@0x7ffffaaf3ea0, terms=@0x7ffffaaf3de0,
 leads_from_strat=@0x7ffffaaf3dc0, log=false, optDrawMatrices=false,
 matrixPrefix=0x2457108 "matrix") at groebner/src/nf.cc:2335
 2335    groebner/src/nf.cc: No such file or directory.
         in groebner/src/nf.cc
 Current language:  auto; currently c++
 (gdb) bt
 #0  linalg_step_modified (polys=@0x7ffffaaf3ea0, terms=@0x7ffffaaf3de0,
 leads_from_strat=@0x7ffffaaf3dc0, log=false, optDrawMatrices=false,
 matrixPrefix=0x2457108 "matrix") at groebner/src/nf.cc:2335
 #1  0x00007f19020cd4b4 in
 polybori::groebner::GroebnerStrategy::faugereStepDense (this=0x35ad520,
 orig_system=<value optimized out>) at groebner/src/nf.cc:2451
 #2  0x00007f1902bda8ed in
 __pyx_pf_4sage_5rings_10polynomial_5pbori_16GroebnerStrategy_faugere_step_dense
 (__pyx_v_self=0x35ad510, __pyx_v_v=<value optimized out>) at
 sage/rings/polynomial/pbori.cpp:32091
 }}}

 More detailed backtrace forthcoming.

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