On Mon, Dec 05, 2016 at 02:36:13PM -0500, DJ Delorie wrote: > > Jan Kurik <jku...@redhat.com> writes: > > Note that coredumpctl is intended as a developer tool, > > As a developer, I remove abrt and anything else that redirects cores > away from my development area. It's really hard to debug a core dump if > you can't find the core file.
You still can restore such behaviour pretty easily. Just set the kernel.core_pattern sysctl. systemd-coredump+coredumpctl give you pretty easy access to core files, they are just dumped into /var/lib/systemd/coredump/. The advantage is that a) things are logged and can be easily looked up and queried, b) you get a lot of metadata like open files, cgroups, /proc/mountinfo, umask, capability masks, etc., c) a stacktrace is automatically generated and logged locally, d) old coredumps are automatically removed, e) you cannot fill your disk with coredumps. The last two points are crucial for "casual" users, who might want to have easy access to the occasional crash without expending too much attention. Zbyszek _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
