#13889: Better automatic backtrace
--------------------------------+-------------------------------------------
Reporter: vbraun | Owner: GeorgSWeber
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.6
Component: build | Resolution:
Keywords: | Work issues:
Report Upstream: N/A | Reviewers:
Authors: Volker Braun | Merged in:
Dependencies: #13881 | Stopgaps:
--------------------------------+-------------------------------------------
Comment (by jdemeyer):
I don't think I know enough about gdb to review this completely, but some
obvious remarks:
1. There is a double "and" in
{{{
"Sage will now try to attach the debugger to get more information and\n"
"and then terminate.\n"
}}}
2. Why should the CSI script kill the Sage process? Couldn't you use a
different IPC mechanism, such as a different signal or a pipe? The
sentence "The target process is frozen while this script runs and resumes
when it is finished." in `sage-CSI` is currently wrong.
3. I preferred how the backtrace currently appears '''before''' the
"Unhandled SIGSEGV: ..." message. When something goes wrong, that message
stands out at the end of the console output. I think all those backtraces
might confuse less experienced Sage users.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13889#comment:6>
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.
