Opened 12 years ago
Closed 12 years ago
#344 closed bug (fixed)
Segment fault by wrong a-ordering with ringlist
Reported by: | Owned by: | somebody | |
---|---|---|---|
Priority: | minor | Milestone: | 3-1-4 and higher |
Component: | dontKnow | Version: | 3-1-3 |
Keywords: | a-ordering, weight | Cc: | daniel.andres@… |
Description
Dear Singular team,
when equipping a ring with an a-ordering using ringlist, one gets a segment fault when using more weights than variables present.
Here is an example.
ring r = 0,(x,y),(a(1..3),dp); r; // no problem // characteristic : 0 // number of vars : 2 // block 1 : ordering a // : names x y // : weights 1 2 // block 2 : ordering dp // : names x y // block 3 : ordering C list RL = ringlist(r); RL[3][1] = list("a",1..3); // three weights for only two vars def rr = ring(RL); setring rr; deg(x); // strange // ==> 4 deg(y); // strange // ==> 5 rr; // characteristic : 0 // number of vars : 2 // block 1 : ordering a // : names x ySingular : signal 11 (v: 3130/ 14130 ): current line:>>rr;<< Segment fault/Bus error occurred at 7f8962965310 because of 10202 (r:1307633446) please inform the authors trying to restart...
Note: See
TracTickets for help on using
tickets.
fixed with revision 14270