#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 SimonKing):
Replying to [comment:6 jdemeyer]:
> I don't think I know enough about gdb
At least you certainly know more than I do. So, sorry for my unqualified
comments...
> 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.
Yes, when an error in Python is raised, one first sees the backtrace and
then the error message. If Sage crashes, it makes sense to show first the
backtrace and then the error message as well.
> I think all those backtraces might confuse less experienced Sage users.
Well, a less experienced Sage user will hopefully never see such
backtraces.
What I mean is: Sage is supposed to run without crashes when doing low-
level stuff. Hence, crashes are supposed to ''only'' occur if the user
creates new buggy Cython programs in Sage, or tries to tweak Sage until it
exposes its existing bugs. And I think a user who does such "real"
programming and developing is experienced enough to not be confused by a
backtrace.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13889#comment:7>
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.
