#2886: [with patch, with positive review] change an error message
----------------------------------+------------------------
Reporter: was | Owner: mhansen
Type: defect | Status: closed
Priority: major | Milestone: sage-3.0
Component: user interface | Resolution: fixed
Keywords: | Merged in:
Authors: | Reviewers:
Report Upstream: N/A | Work issues:
Branch: | Commit:
Dependencies: | Stopgaps:
----------------------------------+------------------------
Changes (by chapoton):
* upstream: => N/A
Old description:
> When you crash Sage you get this error message:
> {{{
> **********************************************************************
>
> Oops, SAGE crashed. We do our best to make it stable, but...
>
> A crash report was automatically generated with the following
> information:
> - A verbatim copy of the crash traceback.
> - A copy of your input history during this session.
> - Data on your current SAGE configuration.
>
> It was left in the file named:
> '/Users/was/.sage/ipython/SAGE_crash_report.txt'
> If you can email this file to the developers, the information in it will
> help
> them in understanding and correcting the problem.
>
> You can mail it to: William Stein at [email protected]
> with the subject 'SAGE Crash Report'.
>
> If you want to do it now, the following command will work (under Unix):
> mail -s 'SAGE Crash Report' [email protected] <
> /Users/was/.sage/ipython/SAGE_crash_report.txt
>
> To ensure accurate tracking of this issue, please file a report about it
> at:
> http://www.sagemath.org:9002/sage_trac
>
> }}}
>
> Issues:
> (1) People need accounts to file a report. It might be much better to
> tell people to report to sage-support.
>
> (2) the url for trac is now trac.sagemath.org/sage_trac
>
> --
>
> I think doing (2) would be fine to fix this ticket.
>
> William
New description:
When you crash Sage you get this error message:
{{{
**********************************************************************
Oops, SAGE crashed. We do our best to make it stable, but...
A crash report was automatically generated with the following information:
- A verbatim copy of the crash traceback.
- A copy of your input history during this session.
- Data on your current SAGE configuration.
It was left in the file named:
'/Users/was/.sage/ipython/SAGE_crash_report.txt'
If you can email this file to the developers, the information in it will
help
them in understanding and correcting the problem.
You can mail it to: William Stein at [email protected]
with the subject 'SAGE Crash Report'.
If you want to do it now, the following command will work (under Unix):
mail -s 'SAGE Crash Report' [email protected] <
/Users/was/.sage/ipython/SAGE_crash_report.txt
To ensure accurate tracking of this issue, please file a report about it
at:
http://www.sagemath.org:9002/sage_trac
}}}
Issues:
(1) People need accounts to file a report. It might be much better to
tell people to report to sage-support.
(2) the url for trac is now trac.sagemath.org/sage_trac
--
I think doing (2) would be fine to fix this ticket.
William
--
--
Ticket URL: <http://trac.sagemath.org/ticket/2886#comment:4>
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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
