#13889: Better automatic backtrace
--------------------------------+-------------------------------------------
       Reporter:  vbraun        |         Owner:  GeorgSWeber
           Type:  enhancement   |        Status:  needs_work 
       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:             
--------------------------------+-------------------------------------------
Changes (by jdemeyer):

  * status:  needs_review => needs_work


Old description:

> When Sage encounters a SIGSEGV, it uses the glibc backtrace. This is
> sometimes seen in doctests that are not reproducible, making it hard to
> debug. The aim of this ticket is to return better automatic stack traces
> by automatically attaching gdb and running scripts in gdb's Python
> interpreter. This will will pinpoint the cause much easier, especially in
> a debug build.
>
> The log is printed to stdout and automatically saved to a log file in
> `$DOT_SAGE/crash_logs` with logs older than a week automatically deleted.
> A sample log is [attachment:sage_crash_wKcUKj.log]
>
> Apply
>   * [attachment:trac_13889_enhanced_backtrace.patch] to Sage library
>   * [attachment:trac_13889_crime_scene_inspector.patch] to the
> `$SAGE_LOCAL/bin` repo

New description:

 When Sage encounters a SIGSEGV, it uses the glibc backtrace. This is
 sometimes seen in doctests that are not reproducible, making it hard to
 debug. The aim of this ticket is to return better automatic stack traces
 by automatically attaching gdb and running scripts in gdb's Python
 interpreter. This will will pinpoint the cause much easier, especially in
 a debug build.

 The log is printed to stdout and automatically saved to a log file in
 `$DOT_SAGE/crash_logs` with logs older than a week automatically deleted.
 A sample log is [attachment:sage_crash_wKcUKj.log]

 Apply
   * [attachment:trac_13889_enhanced_backtrace.patch] and
 [attachment:13889_sagelib_review.patch] to Sage library
   * [attachment:trac_13889_crime_scene_inspector.patch] to the
 `$SAGE_LOCAL/bin` repo

--

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/13889#comment:17>
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.

Reply via email to