Opened 14 years ago
Closed 14 years ago
#4346 closed defect (fixed)
[with patch; with positive review] segmentation fault with set_block
Reported by: | Paul Zimmermann | Owned by: | William Stein |
---|---|---|---|
Priority: | major | Milestone: | sage-3.2 |
Component: | linear algebra | Keywords: | |
Cc: | Merged in: | ||
Authors: | Reviewers: | ||
Report Upstream: | N/A | Work issues: | |
Branch: | Commit: | ||
Dependencies: | Stopgaps: |
Description
---------------------------------------------------------------------- | SAGE Version 3.1.4, Release Date: 2008-10-16 | | Type notebook() for the GUI, and license() for information. | ---------------------------------------------------------------------- sage: M=Matrix([1]) sage: M.set_block(0,1,matrix([1])) ------------------------------------------------------------ Unhandled SIGSEGV: A segmentation fault occured in SAGE. This probably occured because a *compiled* component of SAGE has a bug in it (typically accessing invalid memory) or 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). ------------------------------------------------------------
Attachments (1)
Change History (7)
Changed 14 years ago by
Attachment: | sage-4346.patch added |
---|
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
Summary: | segmentation fault with set_block → [with patch; needs review] segmentation fault with set_block |
---|
comment:3 Changed 14 years ago by
comment:4 Changed 14 years ago by
comment:5 Changed 14 years ago by
Summary: | [with patch; needs review] segmentation fault with set_block → [with patch; with positive review] segmentation fault with set_block |
---|
Looks good, as long as you also apply the patches at #4350.
comment:6 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Merged in Sage 3.2.alpha1
Note: See
TracTickets for help on using
tickets.
The attached patch fixes the problem. However, there are two additional issues, which should be addressed as new tickets.
These are because of bugs in that code exposed by doing proper bounds checking. This is now trac #4351, and must also be fixed before #4346 can go into Sage.
This is now trac #4350.