Opened 9 years ago
Closed 9 years ago
#10179 closed Patch - Feature (Won't Fix)
[PATCH] Produce a core dump file on error in mythfront/backend
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | minor | Milestone: | unknown |
Component: | MythTV - General | Version: | Unspecified |
Severity: | medium | Keywords: | core backtrace |
Cc: | Ticket locked: | no |
Description
Enabling a coredump after a SEGV or similar fault enables a post mortem backtrace to be obtained with gdb, which can be useful in debugging rare problems. See 'man 5 core' for coredump naming etc. See 'man gdb' and search for core
Attachments (1)
Change History (2)
Changed 9 years ago by
Attachment: | coredump.patch added |
---|
comment:1 Changed 9 years ago by
Resolution: | → Won't Fix |
---|---|
Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
It's bad form to enable core dumps within an application. It's easy enough to enable this with ulimit in the startup script, and there you can also set the core pattern so all cores go to a single location that isn't likely to fill up and have knock on effects like crashing your mysql tables.