enable core dumps in openbmc
This has been disabled for a variety of reasons in the past but using
core dumps to debug software failures is an industry norm and therefore
is something openbmc needs to be able to do.
If different companies or meta layers decide they would prefer to leave
this disabled then leave it to be done within their appropriate meta
layer.
Tested:
Generated a core dump, verified it was captured by
phosphor-debug-collector, and that the core could be debugged within an
SDK
(From meta-phosphor rev: 52cd6b9dc4a6c90a7f1531fc9af1f5b4258f8e67)
Change-Id: I18b4af6be584e4508e3aba80903f715b0caec323
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
diff --git a/meta-phosphor/recipes-core/systemd/systemd_%.bbappend b/meta-phosphor/recipes-core/systemd/systemd_%.bbappend
index 0e76c2e..a813a45 100644
--- a/meta-phosphor/recipes-core/systemd/systemd_%.bbappend
+++ b/meta-phosphor/recipes-core/systemd/systemd_%.bbappend
@@ -2,7 +2,7 @@
"${exec_prefix}/lib/systemd/catalog/*.*.catalog"
PACKAGES =+ "${PN}-catalog-extralocales"
PACKAGECONFIG = "pam hostnamed networkd randomseed resolved sysusers timedated \
- timesyncd xz kmod"
+ timesyncd xz kmod coredump"
FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
SRC_URI += "file://default.network"