You do not need to disable abrtd (if you do that, you won't be
able to send crash statistics to http://retrace.fedoraproject.org/).
If you want to use coredumpctl, just disable
abrt-ccpp.service and enable abrt-journal-core.service:
http://abrt.readthedocs.org/en/latest/examples.html#getting-core-files-from-systemd-coredumctl
Regards,
Jakub
On 01/14/2016 05:03 PM, Michael Catanzaro wrote:
You can use ABRT to manage your core dumps, but it's not as nice as
coredumpctl. I recommend disabling ABRT ('systemctl disable abrtd' and
'systemctl stop abrtd') so that your core dumps will appear in
coredumpctl. The ABRT developers are working on better coredumpctl
integration.
On Thu, 2016-01-14 at 13:39 +0300, Roman Tsisyk wrote:
Does it log stack traces with symbol names on crash?
It stores short stack traces with just function names in the system
journal. It stores core dumps temporarily until some size limit is hit,
so you don't have to worry about disk space. You can configure the
limits in /etc/systemd/coredump.conf. In practice this means you get
full stack traces for recent crashes, and simple traces for older ones.
'coredumpctl gdb' is great and you will enjoy it!
Michael
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
