Opened 6 years ago
Closed 6 years ago
#17541 closed defect (wontfix)
Segmentation fault in lrcalc
Reported by: | thansen | Owned by: | sage-combinat |
---|---|---|---|
Priority: | major | Milestone: | sage-duplicate/invalid/wontfix |
Component: | packages: standard | Keywords: | lrcalc |
Cc: | Merged in: | ||
Authors: | Reviewers: | Travis Scrimshaw | |
Report Upstream: | Reported upstream. No feedback yet. | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
Hi,
I have some code that relies heavily on lrcalc and when the input gets more complicated it starts crashing. I managed to find the following minimal code example that usually crashes Sage here (run it repeatedly if it does not crash at once):
import sage.libs.lrcalc.lrcalc as lrcalc def lrcalc_test(): a=lrcalc.coprod([5,4,3,2,1]) b=lrcalc.mult([3,2,0],[0]) c=lrcalc.coprod([0]) d=lrcalc.mult([3,2,0],[0,1])
I am using Sage 6.4.1 (with lrcalc 1.1.7) on Ubuntu 12.04 amd64.
The output of sage is attached.
Attachments (1)
Change History (6)
Changed 6 years ago by
comment:1 Changed 6 years ago by
- Report Upstream changed from Not yet reported upstream; Will do shortly. to Reported upstream. No feedback yet.
comment:2 Changed 6 years ago by
- Milestone changed from sage-6.5 to sage-duplicate/invalid/wontfix
comment:3 Changed 6 years ago by
- Reviewers set to Travis Scrimshaw
- Status changed from new to needs_review
comment:4 Changed 6 years ago by
- Status changed from needs_review to positive_review
While the crash is bad, the fact that you're working directly with the library (after importing it) means we shouldn't worry about it. (In short, I agree.)
comment:5 Changed 6 years ago by
- Resolution set to wontfix
- Status changed from positive_review to closed
Note: See
TracTickets for help on using
tickets.
I just realized that the problem was that [0,1] is invalid input. I changed the milestone to invalid.