Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / d8291e5e6dd3efd53500bde85ed6aa1d1f974904
commitd8291e5e6dd3efd53500bde85ed6aa1d1f974904[log] [tgz]
authorJayanth Othayoth <ojayanth@gmail.com>Thu Nov 30 22:13:46 2023 -0600
committerJayanth Othayoth <ojayanth@gmail.com>Thu Nov 30 22:13:46 2023 -0600
treedb576f32a867f1e4300e2913e3b56b0b7340c4cd
parent7cd0528a38071fe14b224b7a9df13b7a646e9cbe [diff]
owners: updated Jayanth email

Change-Id: I4eb21f20438431134cd3ef2f297e3ce7153adb45
Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
1 file changed
tree: db576f32a867f1e4300e2913e3b56b0b7340c4cd
  1. dump-extensions/
  2. host-transport-extensions/
  3. subprojects/
  4. test/
  5. tools/
  6. .clang-format
  7. .gitignore
  8. .shellcheck-ignore
  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_manager.cpp
  18. dump_manager.hpp
  19. dump_manager_bmc.cpp
  20. dump_manager_bmc.hpp
  21. dump_manager_faultlog.cpp
  22. dump_manager_faultlog.hpp
  23. dump_manager_main.cpp
  24. dump_offload.cpp
  25. dump_offload.hpp
  26. dump_serialize.cpp
  27. dump_serialize.hpp
  28. dump_types.mako.cpp
  29. dump_types.mako.hpp
  30. dump_utils.cpp
  31. dump_utils.hpp
  32. elog_watch.cpp
  33. elog_watch.hpp
  34. example_dump_types.yaml
  35. example_errors_watch.yaml
  36. faultlog_dump_entry.cpp
  37. faultlog_dump_entry.hpp
  38. ffdc
  39. host_transport_exts.hpp
  40. LICENSE
  41. map_gen.py
  42. meson.build
  43. meson.options
  44. OWNERS
  45. ramoops_manager.cpp
  46. ramoops_manager.hpp
  47. ramoops_manager_main.cpp
  48. README.md
  49. watch.cpp
  50. 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.

One such mechanism is dreport, a script that collects debug data and packages it into an archive file.

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