commit | a33b2ab1185d0470998860f71fe5d9a8a1c04815 | [log] [tgz] |
---|---|---|
author | Ben Tyner <ben.tyner@ibm.com> | Fri Feb 05 12:27:19 2021 -0600 |
committer | Ben Tyner <ben.tyner@ibm.com> | Fri Feb 05 12:55:19 2021 -0600 |
tree | d9cbe12a016bce51776b71a5be60633a1188bc24 | |
parent | b6401edf97b29db6662c64c735d495222abbe4a0 [diff] |
Attn: Fix non-null-terminated string in ti handler When copying ascii data from ti info data the resulting string was not being null-terminated. Signed-off-by: Ben Tyner <ben.tyner@ibm.com> Change-Id: I5fc9da3faf34e2760d3353b22fbcb97ba3e553e3
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