commit | 9faf73bae8d4f62d3adda153d407992a2251f655 | [log] [tgz] |
---|---|---|
author | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 01 19:51:35 2020 -0600 |
committer | Zane Shelley <zshelle@us.ibm.com> | Tue Dec 01 19:53:05 2020 -0600 |
tree | 6ece62a3f63f44ec57a93ee3bba018dee0147d85 | |
parent | d3b9bac9e8be6c2989aadc65c6236c9ce1f189ec [diff] |
Fix exception util::transformFFDC() Signed-off-by: Zane Shelley <zshelle@us.ibm.com> Change-Id: I8093bc0d5d46891591501333663d959606ea55fa
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