Opened 8 years ago

Last modified 4 years ago

#1679 new enhancement

Auto-generate backtraces & crash reports

Reported by: vorner Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: Unclassified Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


It would be good if whenever a process crashes, a crash report with some useful information is produced and saved somewhere, noted in a log and the admin is asked to send it. The idea is to use whatever is available in the system to get the information, for example use gdb to attach to the process and get the information or use some built-in methods. The crashing process could have a handler for registered all reasonable fatal signals and call a shell script with it's PID and name and the script would write down system information, call gdb on the PID, produce the backtrace, etc…

It might make sense to register the signals for python too (in case it crashes in the wrapper code) and make sure any uncaught exceptions are caught at the highest level and written down to a file.

I attach a file which does that (from one of my own projects), it is slightly different, it produces the backtrace to the screen and leaves the gdb running, but it can illustrate the idea. While this relies on having gdb installed on the system and having debug information compiled in (which we could enable by default), it would at least increase the chance of getting useful bug report and make it easier for a user to generate them.


Attachments (1)

debug.c (918 bytes) - added by vorner 8 years ago.

Download all attachments as: .zip

Change History (6)

Changed 8 years ago by vorner

comment:1 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Y4 Usability

comment:2 Changed 8 years ago by shane

  • Milestone Y4 Usability deleted

Milestone Y4 Usability deleted

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 5 years ago by tomek

  • Milestone changed from Remaining BIND10 tickets to DHCP Outstanding Tasks
  • Version set to git

comment:5 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.