#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 vbraun):
It makes sense to have the "Unhandled SIGSEGV..." message at the end. I
don't think trying to get back from the debugger into the main program is
a good idea. Sage is currently in a signal handler after something bad
happened, there are no guarantees that anything is still working. In fact,
just calling `printf()` from the signal handler is, strictly speaking,
illegal. But the `sage-CSI` script can easily print the message.
The "The target process is frozen while this script runs and resumes when
it is finished." is correct (unless you add `--kill`, what did you
expect). In fact you can use the `sage-CSI` to see the status of a long-
running computation without disturbing it if you don't pass `--kill`.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13889#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.
