#10113: Calling seed() incorrectly causes Sage to crash with SIGSEGV
(Segmentation
Fault)
------------------------------+---------------------------------------------
Reporter: drkirkby | Owner: jason
Type: defect | Status: needs_review
Priority: major | Milestone: sage-5.0
Component: misc | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Simon King | Merged in:
Dependencies: | Stopgaps:
------------------------------+---------------------------------------------
Comment (by cremona):
Replying to [comment:8 SimonKing]:
> Replying to [comment:7 cremona]:
> > I would be slightly happier if the error message did not refer to
"`__init__`" since the user will not have typed that (probably), but
that's a minor point.
>
> I don't think that the error message can be changed without patching
Python. Theoretically, we could test in `__cinit__` that the number of
arguments for `__init__` is correct - but I think that would be a misuse
of `__cinit__`.
I didn't mean anything so complicated. But I compared for example
{{{
sage: EllipticCurve([1])
...
ValueError: sequence of coefficients must have length 2 or 5
}}}
or
{{{
sage: ZZ(x)
...
TypeError: unable to convert x (=x) to an integer
}}}
which are similar in so far as they are reporting invalid input to a
constructor. It's not serious (and I certainly do not want to detract
from the impressive work you did in tracking this down!).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10113#comment:9>
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.
