#10099: Sage crashes printing copy of symbolic option inside Pynac.
----------------------------------------------------------------------------------+
Reporter: drkirkby
| Owner: AlexGhitza
Type: defect
| Status: positive_review
Priority: major
| Milestone: sage-4.6
Component: algebra
| Keywords:
Author: Mike Hansen
| Upstream: N/A
Reviewer: Karl-Dieter Crisman, David Kirkby, Leif Leonhardy, Francois
Bissey | Merged:
Work_issues:
|
----------------------------------------------------------------------------------+
Comment(by drkirkby):
Replying to [comment:4 kcrisman]:
> WHY you would do `copy(x)` is still open to question, though.
True, but a program should not crash with invalid user input. In fact
generating invalid input is a common way of testing software, to improve
quality. Sometimes it's called ''Fuzz testing'' - see
http://en.wikipedia.org/wiki/Fuzz_testing.
http://www.ibm.com/developerworks/java/library/j-fuzztest.html
says "Fuzz testing is a simple technique that can have a profound effect
on your code quality."
IEEE 610.12:1990. ''Standard Glossary of Software Engineering
Terminology''. defines:
* Error tolerance - the ability of a system or component to continue
normal operating despite the presence of erroneous inputs.
It's actually a common way for hackers to hack software.
Developing some code to feed Sage invalid input to try to crash Sage, or
otherwise leave it in a poor state, would make a very useful student
project!
Dave
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10099#comment:5>
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.
