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

Change-Id: Ie101b6934861e94217f8243749f022d47a3d7427
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
1 file changed
tree: a8b33f71a856134d7c46bd8a9e999bd2b34e389c
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.