Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / 2a6835d765fed0ac8b767193cdb48a7d04ab9f5c
commit2a6835d765fed0ac8b767193cdb48a7d04ab9f5c[log] [tgz]
authorGeorge Liu <liuxiwei@inspur.com>Mon Oct 11 18:59:09 2021 +0800
committerGeorge Liu <liuxiwei@inspur.com>Mon Oct 11 18:59:09 2021 +0800
tree0a35fca7b5e67a14519bca0cc44a8b627676549e
parent9d2d72264319f421d87b2ac93d8e08d84bd9c527 [diff]
ramoops: Check files in pstore

The code was wrong that it passes the pstore dir and create a dump.
Actually it should get the files in pstore dir, and do not create a dump
if it's an empty dir or the dir does not exist.

Signed-off-by: George Liu <liuxiwei@inspur.com>
Change-Id: Id9e2452c93c5e2897441d22d00aeec8b04aca3ee
1 file changed
tree: 0a35fca7b5e67a14519bca0cc44a8b627676549e
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. xyz/
  7. .clang-format
  8. .gitignore
  9. bmc_dump_entry.cpp
  10. bmc_dump_entry.hpp
  11. core_manager.cpp
  12. core_manager.hpp
  13. core_manager_main.cpp
  14. dump-extensions.hpp
  15. dump_entry.cpp
  16. dump_entry.hpp
  17. dump_internal.hpp
  18. dump_manager.cpp
  19. dump_manager.hpp
  20. dump_manager_bmc.cpp
  21. dump_manager_bmc.hpp
  22. dump_manager_main.cpp
  23. dump_offload.cpp
  24. dump_offload.hpp
  25. dump_serialize.cpp
  26. dump_serialize.hpp
  27. dump_utils.cpp
  28. dump_utils.hpp
  29. elog_watch.cpp
  30. elog_watch.hpp
  31. errors_map.mako.hpp
  32. errors_map_gen.py
  33. example_errors_watch.yaml
  34. ffdc
  35. host_transport_exts.hpp
  36. LICENSE
  37. MAINTAINERS
  38. meson.build
  39. meson_options.txt
  40. ramoops_manager.cpp
  41. ramoops_manager.hpp
  42. ramoops_manager_main.cpp
  43. README.md
  44. watch.cpp
  45. watch.hpp
README.md

phosphor-debug-collector

Phosphor Debug Collector provides mechanisms to collect various log files and system parameters. Used to troubleshoot problems in OpenBMC based systems.

To Build

To build this package with meson, do the following steps:

    1. meson builddir
    2. ninja -C builddir

To clean the built files run ninja -C builddir clean.

To run unit tests

Tests can be run in the CI docker container, refer local-ci-build

or with an OpenBMC x86 sdk(see below for x86 steps).

meson -Dtests=enabled build
ninja -C build test