Opened 10 years ago

Last modified 10 years ago

#13889 closed enhancement

Better automatic backtrace — at Version 2

Reported by: Volker Braun Owned by: Georg S. Weber
Priority: major Milestone: sage-5.7
Component: build Keywords:
Cc: Simon King Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by Volker Braun)

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 sage_crash_wKcUKj.log

Apply

Change History (2)

comment:1 Changed 10 years ago by Volker Braun

Description: modified (diff)

comment:2 Changed 10 years ago by Volker Braun

Description: modified (diff)
Note: See TracTickets for help on using tickets.