Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / phosphor-debug-collector / e22aca712e024a8989d4d0f2c6235513abb06d13
commite22aca712e024a8989d4d0f2c6235513abb06d13[log] [tgz]
authorChirag Sharma <chirshar@in.ibm.com>Mon Jan 18 09:55:29 2021 -0600
committerJayanth Othayoth <ojayanth@in.ibm.com>Tue Feb 02 04:05:41 2021 +0000
tree95b2ee942b4a40f290ba00965e63bc14f887ad37
parent24e0c5910af87fac22c08dd61d2315cd98c56fcd [diff]
Renaming ubifs-workaround flag to jffs-workaround

Changes:
Renaming the ubifs-workaround flag to jffs-workaround.
Default behaviour is IN_CREATE, if jffs-workaround is enabled
will monitor for IN_CLOSE_WRITE.

Test:
Tested the fix on romulus i.e. jffs2, ext4 and ubifs. The core file
is getting transferred to dump folder.
Also did full build for jffs and ext4 fs.

Change-Id: I964f5923ad73926db214526aa6c62fca9ac90ba8
Signed-off-by: Chirag Sharma <chirshar@in.ibm.com>
3 files changed
tree: 95b2ee942b4a40f290ba00965e63bc14f887ad37
  1. dump-extensions/
  2. host-transport-extensions/
  3. test/
  4. tools/
  5. xyz/
  6. .clang-format
  7. .gitignore
  8. bmc_dump_entry.cpp
  9. bmc_dump_entry.hpp
  10. core_manager.cpp
  11. core_manager.hpp
  12. core_manager_main.cpp
  13. dump-extensions.hpp
  14. dump_entry.cpp
  15. dump_entry.hpp
  16. dump_internal.hpp
  17. dump_manager.cpp
  18. dump_manager.hpp
  19. dump_manager_bmc.cpp
  20. dump_manager_bmc.hpp
  21. dump_manager_main.cpp
  22. dump_offload.cpp
  23. dump_offload.hpp
  24. dump_serialize.cpp
  25. dump_serialize.hpp
  26. dump_utils.cpp
  27. dump_utils.hpp
  28. elog_watch.cpp
  29. elog_watch.hpp
  30. errors_map.mako.hpp
  31. errors_map_gen.py
  32. example_errors_watch.yaml
  33. ffdc
  34. host_transport_exts.hpp
  35. LICENSE
  36. MAINTAINERS
  37. meson.build
  38. meson_options.txt
  39. README.md
  40. watch.cpp
  41. 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 -Doe-sdk=enabled -Dtests=enabled build
ninja -C build test