Changes between Version 17 and Version 18 of Ticket #13889


Ignore:
Timestamp:
Jan 12, 2013, 9:44:18 PM (10 years ago)
Author:
Jeroen Demeyer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13889 – Description

    v17 v18  
    11When 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.
    22
    3 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]
     3The 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.
    44
    55Apply