Hardware error analyzer for checkstop analyses
When a checkstop occurs the attention handler will use the hardware
error isolator to gather information pertaining to the error
condition(s).
Signed-off-by: Ben Tyner <ben.tyner@ibm.com>
Change-Id: If933be6bddfc653edf0ed3db660c32d3aae04c5f
diff --git a/main_nl.cpp b/main_nl.cpp
index 1eead08..d66e378 100644
--- a/main_nl.cpp
+++ b/main_nl.cpp
@@ -44,6 +44,14 @@
}
else
{
+ // Pdbg targets should only be initialized once according to
+ // libpdbg documentation. Initializing them here will make sure
+ // they are initialized for the attention handler, invocation of
+ // the analyzer via attention handler and direct invocation of
+ // the analyzer via command line (--analyze).
+
+ pdbg_targets_init(nullptr); // nullptr == use default fdt
+
// Either analyze (application mode) or daemon mode
if (true == getCliOption(argv, argv + argc, "--analyze"))
{
@@ -52,7 +60,7 @@
rc = analyzer::analyzeHardware(errors); // analyze hardware
- printf("analyzer isolated %i errors", (int)errors.size());
+ printf("analyzer isolated %i error(s)\n", (int)errors.size());
}
// daemon mode
else