Opened 14 years ago

Closed 14 years ago

#288 closed bug (fixed)

redSB leads to infinite loop in std

Reported by: Oleksandr Owned by: hannes
Priority: major Milestone: 3-1-2 and higher
Component: singular-kernel Version: 3-1-1
Keywords: Cc:

Description (last modified by Oleksandr ) 

> ring r = 0, (y), (a(-1), dp); y+1;
1+y
> std(ideal(1+y));
_[1]=1+y
> option(redSB); // due to this "reduced SB" option
> std(ideal(1+y)); // std never stops!!!

the Singularg outputs (in an endless loop): 

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dc6baf0 size:40 allocated at  ../kernel/pInline1.h:100

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dcd2230 size:40 allocated at  ../kernel/p_Copy__T.cc:25

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dcd2230 size:40 allocated at  ../kernel/p_Copy__T.cc:25

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dc6baf0 size:40 allocated at  ../kernel/pInline1.h:100

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dcd2380 size:40 allocated at  ../kernel/p_Copy__T.cc:25

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dcd2380 size:40 allocated at  ../kernel/p_Copy__T.cc:25

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dc6baf0 size:40 allocated at  ../kernel/pInline1.h:100

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dcd24d0 size:40 allocated at  ../kernel/p_Copy__T.cc:25

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dcd24d0 size:40 allocated at  ../kernel/p_Copy__T.cc:25

// ***dPolyError: monoms p and p->next are equal 
 occured at
 occured for poly:  addr:0x7f552dc6baf0 size:40 allocated at  ../kernel/pInline1.h:100

and so on...

Change History (3)

comment:1 Changed 14 years ago by Oleksandr

btw, 

ring r = 0, (y), (ls);

or 

ring r = 0, (y), (ds);

do NOT expose this behavior.

the weighting vector with negative entries seems to be guilty...

comment:2 Changed 14 years ago by Oleksandr

Description: modified (diff)

comment:3 Changed 14 years ago by hannes

Resolution: → fixed
Status: new → closed

missing cancelunit added

Note: See TracTickets for help on using tickets.