Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-hw-diags / 5836f4a69bf9184126ea84dd9d5f8b6490051727
commit5836f4a69bf9184126ea84dd9d5f8b6490051727[log] [tgz]
authorZane Shelley <zshelle@us.ibm.com>Thu Feb 09 14:28:08 2023 -0600
committerZane Shelley <zshelle@us.ibm.com>Thu Feb 09 14:31:28 2023 -0600
treea0d089e119b5eaf1745d2c4b3eb4b58cf34cdc18
parent02d59af5419a8d262d226be4febd3e70c7942be2 [diff]
use nholmann json exceptions instead of std

nholmann::json::at() will throw nholmann::json::out_of_range instead
of std::out_of_range. This resulted in missed exceptions in the
signature filtering code.

Change-Id: I573e1ed4455bbda4f05c100edd315eb0ccdc9c3f
Signed-off-by: Zane Shelley <zshelle@us.ibm.com>
2 files changed
tree: a0d089e119b5eaf1745d2c4b3eb4b58cf34cdc18
  1. analyzer/
  2. attn/
  3. subprojects/
  4. test/
  5. util/
  6. .clang-format
  7. .eslintignore
  8. .gitignore
  9. .prettierignore
  10. .prettierrc.yaml
  11. buildinfo.hpp.in
  12. cli.cpp
  13. cli.hpp
  14. config.h.in
  15. LICENSE
  16. listener.cpp
  17. listener.hpp
  18. main.cpp
  19. main_nl.cpp
  20. meson.build
  21. meson_options.txt
  22. OWNERS
  23. README.md
README.md

Hardware Diagnostics for POWER Systems

In the event of a system fatal error reported by the internal system hardware (processor chips, memory chips, I/O chips, system memory, etc.), POWER Systems have the ability to diagnose the root cause of the failure and perform any service action needed to avoid repeated system failures.

Aditional details TBD.

Building

For a standard OpenBMC release build, you want something like:

meson -Dtests=disabled <build_dir>
ninja -C <build_dir>
ninja -C <build_dir> install

For a test / debug build, a typical configuration is:

meson -Dtests=enabled <build_dir>
ninja -C <build_dir> test