commit | cb766a45aa79267b8df0bb82be89bbaa3cfc11eb | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 12 17:50:23 2022 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Wed Jan 12 17:50:23 2022 -0600 |
tree | c5e22cb88c43993b2c1b48bb14162489635ca1a2 | |
parent | afc6acda80df62cc0d288467419dd9b1307a8b40 [diff] |
convert resolution_test.cpp to use pdbg library Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: Ibdaa0cf34dd45c75e95ef334793d2adfe41b1f85
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.
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